Server Quality Checklist

Tool Scores

• dbconvert_get_connectionA
  4.2/5.0
  Behavior5/5

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

  Beyond the safe-read annotations, the description provides critical behavioral context: credentials are structurally absent, not redacted, and impossible to retrieve through MCP. It also warns the agent to report only fields present in the response, which aligns with the openWorldHint annotation. No contradiction with 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 two tight sentences with zero fluff. The core purpose is front-loaded, and the security caveat is concisely stated without redundancy.

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

  Completeness4/5

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

  For a simple get-by-id tool with an output schema, safe-read annotations, and a single documented parameter, the description is nearly complete. The only minor gap is that it does not point the agent to the sibling list tool as a source for obtaining a connectionId.

  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% and the single parameter connectionId is already described in the schema as 'Stored DBConvert connection ID'. The description adds no new parameter-level meaning, so the baseline of 3 is appropriate.

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

  Purpose5/5

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

  The description uses a specific verb ('Get'), names the resource ('one connection'), and enumerates exactly what fields are returned. It also implicitly distinguishes itself from the sibling list tool by focusing on a single connection rather than listing data sources.

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

  Usage Guidelines3/5

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

  The description makes clear this tool targets one specific connection, which implies when to use it versus listing tools. However, it does not explicitly mention the sibling dbconvert_list_data_sources or state when not to use this tool, leaving the routing decision to inference.

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

• dbconvert_list_data_sourcesA
  4.5/5.0
  Behavior4/5

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

  Annotations already indicate a read-only, non-destructive operation. The description adds meaningful behavioral context beyond these annotations: each item has exactly four fields, secrets are never exposed, and the agent must not fabricate fields. This is useful guidance for correctly interpreting tool output.

  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 three sentences with no filler. Purpose is front-loaded, sibling routing follows, and the anti-fabrication instruction is precise. Every sentence contributes to correct tool usage.

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

  Completeness5/5

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

  For a read-only list tool with one optional parameter and an existing output schema, the description covers the purpose, exact return shape, sibling distinction, and security caveat. Nothing necessary for correct invocation is missing.

  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 only parameter, limit, is fully documented in the input schema with default and maximum values, so schema coverage is 100%. The description does not add parameter-level detail, but none is needed because the schema already carries the full meaning.

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

  Purpose5/5

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

  The description states a specific verb and resource: 'List DBConvert Streams connections.' It goes further than the tool name by enumerating the exact item fields and explicitly distinguishing this tool from dbconvert_get_connection. An agent can immediately tell what type of operation this is and what it returns.

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

  Usage Guidelines5/5

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

  The description explicitly routes the agent to the sibling tool: 'For host/port/username and other connection details use get_connection.' It also clarifies that passwords and cloud keys are never exposed by any tool, setting correct expectations about what not to attempt here.

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