Vendors in category

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

Annotations already declare 'readOnlyHint' and 'openWorldHint', describing safety and open-world nature. The description adds minimal extra behavior ('vendor summaries') but does not disclose pagination, rate limits, or other traits. With annotations covering the core profile, a 3 is appropriate.

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

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

A single sentence with a parenthetical example and cross-reference to 'list_categories'. No extraneous content; every word earns its place.

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

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

For a simple list tool with one parameter, no output schema, and safety annotations, the description is sufficient. It explains the purpose, parameter source, and an example. Minor gap: does not clarify if results are paginated or limited, but not critical given the tool's simplicity.

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

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

Schema coverage is 100% and the schema description for 'category' is 'Category slug.' The description repeats the example slug but adds no new semantic info beyond what the schema provides. Baseline 3 for full schema coverage.

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

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

The description clearly states the action ('List vendor summaries') and the resource ('in a category'), with a concrete example ('e.g. 'finance-and-payments''). It also references 'list_categories' to help obtain the slug, distinguishing it from siblings like 'search_vendors' or 'get_vendor'.

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

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

The description explicitly directs users to use 'list_categories' to obtain the correct category slug, providing context on how to use this tool. While it does not explicitly state when not to use it, the specificity of listing vendors in a category implies its niche compared to broader tools like 'search_vendors'.

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