Listar produtos

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

The description adds value beyond annotations by specifying the exact fields returned (name, price, status, type) and the scope (authenticated ZuckPay account). Annotations already provide readOnlyHint and openWorldHint, but the description offers concrete output context without contradicting any 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 only two sentences, front-loaded with purpose and key details. Every word adds value: first sentence lists the resource and returned fields, second sentence clarifies read-only nature. No wasted content.

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 optional parameter, the description covers purpose, scope, read-only nature, and output fields. However, it does not explicitly explain pagination behavior (e.g., that 'limit' controls page size) or mention that multiple pages may exist. The schema covers the parameter, but a brief note on pagination would improve completeness.

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 the 'limit' parameter fully described in the schema (min, max, default). The description does not mention the parameter, but since the schema already provides complete semantics, the description adds no extra parameter meaning. Baseline of 3 is appropriate.

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 tool lists registered products from the authenticated ZuckPay account, specifying the included fields (name, price, status, type). It distinguishes itself from the sibling 'getProduct' which likely retrieves a single product, though not explicitly. The read-only clarification further differentiates it from write tools.

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 indicates read-only use for listing products, which implies when to use it, but it does not provide explicit guidance on when not to use it or alternatives (e.g., 'getProduct' for single product). Usage context is implied rather than clearly stated.

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