Server Quality Checklist

Tool Scores

• search_vendorsA
  4.1/5.0
  Behavior3/5

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

  The description adds important behavioral context: the query is a substring match across name/category/owner, while category and status are exact filters. However, without annotations, it does not disclose behaviors such as pagination, result limits, or behavior when no query is provided (e.g., returns all vendors). These gaps make it adequate but not fully transparent.

  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 concise and front-loaded: two short sentences that immediately convey the core functionality and the optional filters. There is no redundant or filler content.

  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?

  The description covers the main search and filter features, and an output schema exists, so return values are documented. However, it does not explain how query and filters combine (AND vs OR), nor the behavior when the query is omitted. These are important for effective invocation, leaving a clear gap.

  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?

  Schema coverage is 0%, so the description must compensate. It clarifies the semantics of the 'query' parameter (substring across fields), and the 'category' and 'status' parameters (exact filters). The 'limit' parameter is not mentioned, but its schema provides min/max/default, so the description adds value for the ambiguous parameters.

  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 the tool's function: 'Search vendor records by a name, category, or owner substring.' It specifies the resource (vendor records), the actions (substring search and optional exact filters), and gives enough detail to distinguish it from a generic search tool.

  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?

  No sibling tools are listed, so explicit alternatives are not applicable. The description provides clear context on when to use the tool (searching vendors with substring or exact filters) and implies that filtering is optional. There are no exclusions or when-not guidance, but the purpose is clear enough for a standalone tool.

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