Listar transações

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

Annotations already declare readOnlyHint and openWorldHint. The description adds significant behavioral context: ordering (newest first), pagination via cursor with limits, timezone (Brasília), and a strong warning against bulk loading. 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?

Description is relatively concise (one long sentence) and front-loaded with the core purpose. It efficiently packs ordering, filters, pagination, cursor, timezone, and a warning. Slight improvement possible by breaking into shorter sentences or bullet points, but it remains clear and readable.

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 8 parameters, no required params, 100% schema coverage, no output schema, and 18 sibling tools, the description covers all essential usage aspects: what is listed, ordering, all filter dimensions, pagination mechanics, timezone, and explicit guidance against loading all data at once. Highly complete for an agent to use correctly.

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 detailed descriptions. The tool description restates the filtering capability (status, type, payment method, external ID, period) but does not add new semantic meaning beyond what the schema already provides. Baseline 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?

Clearly states the tool lists transactions (vendas e saques) from the authenticated ZuckPay account, ordered newest to oldest, with multiple filters. Differentiates from sibling tools like getSalesToday or getTransactionStatus by listing all transactions with pagination and extensive filtering.

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 instructs to use cursor pagination, load one page at a time, and not attempt to load all at once. Provides clear usage context (filters, timezone). However, does not explicitly state when to prefer this over sibling tools like getSalesToday (specific focus) or getTransactionStatus (single transaction). A short 'when-to-use' would improve differentiation.

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