Listar links de pagamento

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

Annotations already provide readOnlyHint=true and openWorldHint=true, so the description's read-only disclosure adds no new safety info. It does add context about the scope (authenticated account) and listed fields, but this is marginal beyond 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?

Single sentence, front-loaded with the verb 'Lista', includes key details without any unnecessary words. Every part of the description carries meaning.

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?

Given the simple input schema (one parameter), complete annotations, and no output schema, the description covers the essential behavior. Minor gap: does not describe the return format (list of objects) or pagination details, but these are inferred from the action and parameter.

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 only parameter (limit) has 100% schema description coverage, fully explaining its range and default. The tool description does not add any extra meaning beyond the schema, so baseline score of 3 applies.

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?

Description clearly states it lists payment links from the authenticated ZuckPay account, specifying fields (nome, valor, status, slug, visualizações). This is a specific verb+resource scope that distinguishes it from sibling tools like createPixCharge or listTransactions.

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?

Explicitly states 'Somente leitura — não cria nem edita links' (read-only — does not create or edit links), giving clear when-to-use and when-not-to-use guidance. While it does not name alternative tools, the context from sibling names provides implicit differentiation.

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