Server Quality Checklist

Tool Scores

• get_datamartC
  2.8/5.0
  Behavior2/5

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

  No annotations provided; the description does not disclose side effects, permissions, rate limits, or error handling. It only notes that SQL and metadata may not always be available ('when available'), which is a minor behavioral detail but insufficient for a complete transparency.

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

  Conciseness4/5

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

  The description is a single, concise sentence that conveys the core purpose without unnecessary words. It could benefit from a brief note on output but remains efficient.

  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 only one parameter, no output schema, and no annotations, the description is minimally adequate. It states what is fetched but omits details on return format, error conditions, and integration points. A more complete description would include expected output structure and potential failures.

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

  Parameters2/5

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

  With 0% schema description coverage, the description should add meaning to the parameter. It only mentions 'by datamart_definition_id', which repeats the parameter name without explaining its format, constraints, or relationship to the tool's behavior. The schema already defines it as integer with exclusiveMinimum, so the description adds no value.

  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 (Fetch) and resource (TROCCO datamart definition), specifying what is included (BigQuery SQL and option metadata). It distinguishes from the sibling get_workflow implicitly by focusing on datamart, but lacks explicit differentiation.

  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 on when to use this tool versus alternatives, no prerequisites, and no conditions for use. The sibling 'get_workflow' exists but no comparison is provided.

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

• get_workflowA
  3.7/5.0
  Behavior3/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 'read-only,' indicating no side effects, which is a useful behavioral hint. However, it does not disclose other traits such as error handling (e.g., what happens if pipeline_definition_id is missing or invalid), authorization requirements, or idempotency. The description adds some transparency but lacks completeness.

  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, well-structured sentence of 15 words. It front-loads the verb and resource, and every word is informative. There is no redundancy or filler, making it highly concise and efficient.

  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 (one parameter, no output schema), the description provides the basic purpose and context. However, it omits important details such as the return format, potential errors, or prerequisites. For an AI agent to invoke it correctly, more information about what the response contains would be helpful. The description is too minimal for full completeness.

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

  Parameters2/5

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

  The schema has 0% description coverage, meaning the description does not elaborate on the parameter pipeline_definition_id beyond mentioning it by name. The schema defines it as an integer with exclusiveMinimum 0, but the description adds no additional meaning about its purpose, format, or constraints. With such low coverage, the description should compensate, but it fails to do so.

  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 clearly states 'Fetch a TROCCO workflow definition by pipeline_definition_id for read-only audit preparation.' It specifies the verb (Fetch), the resource (workflow definition), the identifier (pipeline_definition_id), and the context (read-only audit preparation). This distinguishes it from the sibling tool get_datamart, which operates on a different resource.

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

  Usage Guidelines4/5

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

  The description provides context by stating 'for read-only audit preparation,' which implies when to use this tool (audit scenarios). However, it does not explicitly exclude alternative uses or compare against the sibling tool get_datamart. The guidance is clear but not comprehensive enough for a score of 5.

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