GET /suppliers (Supplier)

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds behavioral details about pagination behavior depending on the limit parameter and the ability to pass multiple values as comma-separated strings. 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.

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

The description is concise, with the core purpose upfront and a clear warning. It could be slightly more efficient, but no extraneous information.

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?

With no output schema, the description does not explain return values or structure. It covers input pagination but omits output fields. Given the complexity of a listing tool with multiple filters, this is a notable gap.

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% with descriptions for each parameter, but the description adds meaningful usage context: the warning about the limit parameter for new pagination and the note that array items accept comma-separated values, which goes beyond the schema descriptions.

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 'Listagem paginada de Fornecedores' (paginated listing of suppliers), with a specific verb (listagem) and resource (fornecedores). It distinguishes from siblings like get_supplier (single) and other list_* tools by specifying the resource, and adds pagination context.

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 provides explicit guidance on using the limit parameter for the new pagination model, including a note about its future deprecation. However, it does not explicitly state when to choose this tool over sibling list tools, though resource naming makes it clear.

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