get_vendors

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

No annotations are provided, so the description must disclose behavioral traits, but it only states 'List all vendors' and the parameters. It does not mention whether the operation is read-only, any rate limits, or pagination behavior beyond the basic 'page' and 'per_page' parameters.

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?

The description is extremely concise, with a clear front-loaded purpose statement followed by succinct parameter definitions. There is no unnecessary verbiage or redundancy.

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 paginated list tool, the description covers the essential behavior. The output schema is available to define the response structure, so the lack of return-value details is acceptable. However, it omits any mention of ordering or filtering capabilities, which could be useful.

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?

The description explicitly explains both parameters ('Page number' and 'Results per page'), which the input schema lacks. This adds meaningful semantic value beyond the schema's type and default information.

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 'List all vendors' with a specific verb (list) and resource (vendors). This unambiguously conveys the tool's function, and while there are no vendor-specific sibling tools, the purpose is distinct and easily understood.

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 does not explicitly state when to use this tool versus alternatives, but the simple list operation implies its use when vendor data is needed. No exclusions or alternative tool references are provided, making the guidance implicit rather than explicit.

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