Server Quality Checklist

Tool Scores

• Behavior2/5

  Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

  With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions execution but doesn't specify whether this is read-only or can modify data, what permissions are required, potential rate limits, error handling, or output format. For a tool that executes arbitrary SQL queries, this lack of transparency is a significant gap.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is extremely concise at just four Chinese characters, with zero wasted words. It's front-loaded with the core action and resource. While potentially too brief for completeness, it earns full marks for conciseness and structure.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness2/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Given the complexity of executing arbitrary SQL queries, no annotations, no output schema, and sibling tools that suggest database operations, the description is inadequate. It doesn't address critical context like connection requirements, safety considerations, or what happens when queries fail. The description should do more to help an agent use this tool correctly.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema description coverage is 100%, with clear documentation for both parameters ('query' and 'limit'). The description doesn't add any meaningful semantic information beyond what the schema already provides, such as query syntax examples or limit implications. Baseline 3 is appropriate when the schema does the heavy lifting.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose3/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description '執行 SQL 查詢語句' (Execute SQL query statement) clearly states the tool's action (execute) and resource (SQL query), but it's vague about scope and doesn't distinguish from siblings like 'describe-table' or 'list-tables' which also involve database operations. It provides basic purpose but lacks specificity about what kind of queries or databases it works with.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines2/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description provides no guidance on when to use this tool versus alternatives like 'describe-table' or 'list-tables', nor does it mention prerequisites such as needing an active database connection. It simply states what the tool does without context about appropriate use cases or exclusions.

  Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

• Behavior2/5

  Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

  With no annotations provided, the description carries full burden for behavioral disclosure. It states the action ('connect') but reveals nothing about what happens after connection: whether it establishes a persistent session, returns a connection object, handles authentication errors, or has rate limits. For a critical operation like database connection, this lack of behavioral context is a significant gap.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a single, efficient sentence in Chinese that directly states the tool's function without any fluff or redundancy. It's appropriately sized for a straightforward connection tool and gets straight to the point.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness2/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  For a database connection tool with 7 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what the connection enables (e.g., subsequent queries), what format the connection takes, or error handling. Given the complexity and lack of structured data, more context about the connection lifecycle and behavioral outcomes is needed.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  The schema has 100% description coverage, providing detailed documentation for all 7 parameters including defaults and requirements. The description adds no parameter-specific information beyond implying MSSQL as the database type, which is already evident from the schema. This meets the baseline of 3 for high schema coverage.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose4/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description '連接到 MSSQL 資料庫伺服器' clearly states the verb ('連接' meaning 'connect') and resource ('MSSQL 資料庫伺服器'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'switch-database' or 'connection-status', which would require more specific language about establishing a new connection versus managing existing ones.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines2/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing server credentials), when not to use it (e.g., if already connected), or how it relates to siblings like 'disconnect' or 'switch-database'. This leaves the agent with minimal context for tool selection.

  Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

• Behavior2/5

  Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

  With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a read operation ('查看' - view), implying it's non-destructive, but doesn't mention authentication requirements, rate limits, error conditions, or what the output contains (e.g., column names, types, constraints). For a metadata tool with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a single, efficient sentence in Chinese that directly states the tool's purpose without any fluff. It's appropriately sized and front-loaded, with every word contributing to understanding what the tool does. No wasted space or unnecessary elaboration.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness2/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Given the tool's moderate complexity (metadata inspection with 2 parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what '欄位結構' (field structure) includes, potential output format, error handling, or dependencies on other tools like 'connect-database'. For a tool that likely returns detailed schema information, more context is needed to use it effectively.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema description coverage is 100%, with both parameters ('schemaName' and 'tableName') clearly documented in the schema. The description adds no additional parameter information beyond implying a 'tableName' is required. Since the schema does the heavy lifting, the baseline score of 3 is appropriate—the description doesn't compensate but doesn't need to given the comprehensive schema documentation.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose4/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description '查看指定資料表的欄位結構' (View the field structure of a specified table) clearly states the tool's purpose with a specific verb ('查看' - view) and resource ('資料表的欄位結構' - table's field structure). It distinguishes this as a metadata inspection tool rather than a data query or connection management tool, though it doesn't explicitly differentiate from potential sibling tools like 'list-tables' beyond the obvious scope difference.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines2/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description provides no guidance on when to use this tool versus alternatives. While the purpose is clear, there's no mention of prerequisites (e.g., needing an active database connection), when this tool is appropriate versus 'list-tables' or 'execute-query', or any constraints on its use. The agent must infer usage from context alone.

  Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

• Behavior2/5

  Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

  No annotations are provided, so the description carries the full burden. It states the action ('switch') but doesn't disclose behavioral traits such as whether this requires authentication, if it's destructive (e.g., closes previous connections), error conditions, or what happens on success. This leaves critical operational details unspecified for a mutation tool.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a single, efficient sentence in Chinese ('切換到指定的資料庫'), which is appropriately sized and front-loaded with the core action. There is no wasted verbiage or structural issues.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness2/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Given the tool's complexity (a mutation with no annotations and no output schema), the description is incomplete. It lacks details on behavior, side effects, prerequisites, and expected outcomes, making it inadequate for safe and effective use by an AI agent in this context.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters4/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  The description adds minimal meaning beyond the input schema, which has 100% coverage and documents the single parameter 'database' as '要切換到的資料庫名稱' (the database name to switch to). With zero parameters undocumented, the baseline is 4, as the description doesn't need to compensate but also doesn't enhance parameter understanding significantly.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose3/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description '切換到指定的資料庫' (switch to the specified database) states a clear verb ('switch') and resource ('database'), but it's vague about what 'switch' means operationally. It doesn't distinguish from siblings like 'connect-database' or 'list-databases', leaving ambiguity about whether this establishes a new connection or changes an active session.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines2/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  There is no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing connection), exclusions, or relationships to siblings like 'connect-database' for initial setup or 'disconnect' for cleanup. The agent must infer usage from context alone.

  Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

• Behavior2/5

  Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

  No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool checks connection status, implying a read-only operation, but doesn't specify what information is returned (e.g., success/failure, latency, error details), whether it requires authentication, or if it has side effects. This leaves significant gaps in understanding the tool's behavior.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a single, clear sentence in Chinese that directly states the tool's purpose without any unnecessary words or structural fluff. It is front-loaded and efficiently communicates the core function, making it highly concise and well-structured.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness2/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimal but adequate for basic understanding. However, it lacks details on what the check entails (e.g., returns a boolean, detailed status, or error), making it incomplete for an agent to fully anticipate the tool's behavior without additional context.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters4/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  The input schema has 0 parameters with 100% coverage, meaning no parameters are documented. The description doesn't mention any parameters, which is appropriate since none exist. It earns a baseline 4 because it doesn't need to compensate for missing parameter info, but loses a point for not explicitly noting the lack of inputs.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose4/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description clearly states the action ('檢查' meaning 'check' or 'inspect') and the target ('資料庫連接狀態' meaning 'database connection status'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'connect-database' or 'disconnect', which also relate to connection management, so it doesn't reach the highest clarity level.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines2/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., whether a connection must be established first), exclusions, or comparisons to siblings like 'connect-database' for establishing connections or 'disconnect' for terminating them, leaving the agent with minimal context for selection.

  Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

• Behavior2/5

  Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

  No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool lists tables but doesn't describe what 'current database' means, whether it requires an active connection, how results are formatted, or if there are limitations (e.g., pagination). For a tool with zero annotation coverage, this is a significant gap in transparency.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a single, efficient sentence in Chinese: '列出目前資料庫中的所有資料表'. It is front-loaded with the core action and resource, with zero wasted words or redundancy, making it highly concise and well-structured.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness2/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Given the complexity (a read operation with no parameters) and the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'current database' refers to, whether a connection is required, or what the output looks like (e.g., a list of table names). For a tool with no structured support, more context is needed to be fully helpful.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters4/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  The tool has 0 parameters, and the schema description coverage is 100% (since there are no parameters to describe). The description doesn't need to add parameter details, so it meets the baseline of 4 for tools with no parameters, as it doesn't have to compensate for any schema gaps.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose4/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description clearly states the tool's purpose: '列出目前資料庫中的所有資料表' (List all tables in the current database). It specifies the verb '列出' (list) and the resource '資料表' (tables), making the action clear. However, it doesn't explicitly differentiate from sibling tools like 'list-databases' or 'describe-table', which would require a 5.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines2/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a database connection), exclusions, or comparisons to siblings like 'list-databases' (which lists databases) or 'describe-table' (which describes a specific table). This leaves usage context ambiguous.

  Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

• Behavior2/5

  Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

  With no annotations provided, the description carries full burden for behavioral disclosure. '斷開資料庫連接' implies a destructive operation that terminates a connection, but it doesn't specify whether this requires an active connection first, what happens to pending queries, or if the operation is reversible. For a potentially destructive tool with zero annotation coverage, this is insufficient.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a single, efficient phrase ('斷開資料庫連接') that directly states the tool's purpose with zero wasted words. It's appropriately sized and front-loaded for a simple, parameterless operation.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness3/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Given the tool's simplicity (0 parameters, no output schema), the description is minimally adequate. However, as a potentially destructive operation with no annotations, it should ideally mention prerequisites (e.g., requires an active connection) or effects. The absence of output schema isn't critical here since the action is straightforward.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters4/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the absence of parameters. The description doesn't need to add parameter information, and the baseline for 0 parameters is 4. No additional semantic value is required or provided.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose4/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description '斷開資料庫連接' (Disconnect database connection) clearly states the action (disconnect) and target (database connection), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'connect-database' or 'connection-status', which would require a 5.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines2/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description provides no guidance on when to use this tool versus alternatives. There are no explicit when/when-not instructions or references to sibling tools like 'connect-database' or 'connection-status' that handle related database connection operations.

  Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

• Behavior2/5

  Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

  No annotations are provided, so the description carries the full burden. It states what the tool does but lacks behavioral details such as whether it requires authentication, how results are formatted (e.g., list of names, JSON), if there are rate limits, or if it's a read-only operation. The description is minimal and doesn't compensate for the lack of annotations.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a single, clear sentence that directly states the tool's purpose with zero waste. It's appropriately sized and front-loaded, making it easy to understand at a glance.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness3/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is adequate but has gaps. It covers the basic purpose but lacks context on usage, behavioral traits, or output format. For a list operation with no structured data, more guidance would be helpful, but it meets the minimum viable threshold.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters4/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate here. A baseline of 4 is applied since there are no parameters to document, and the description doesn't introduce confusion.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose4/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description '列出伺服器上的所有使用者資料庫' clearly states the action (list) and target (user databases on the server). It's specific enough to understand the tool's function, though it doesn't explicitly differentiate from sibling tools like 'list-tables' or 'describe-table' beyond the scope of databases vs. tables.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines2/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a connection first), exclusions, or comparisons to siblings like 'list-tables' (which lists tables within a database) or 'describe-table' (which describes table structure).

  Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.