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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds behavioral context by stating this is a 'Leitura' (read) operation for the legacy API, mentioning filter support via JSON data, and highlighting bulk support with transaction_ids. No contradictions 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 verbose, listing many actions not specific to this tool (e.g., list_transactions, list_subscriptions). The important information is present but buried. The '[Flattened action]' line helps, but the overall structure could be more concise and targeted.

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?

The description provides context about the legacy API and filter capabilities, but lacks details on the output format or return values (no output schema). It covers the when-to-use aspect well, but given the complexity and number of sibling tools, more detail on the response structure 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?

Input schema has 0% description coverage. The description adds meaning by explaining that the 'data' parameter accepts JSON for filters (count, page, status), and that 'transaction_ids' is for batch execution. However, the 'account' parameter is not explained, and the description does not fully detail each parameter's format or constraints. Partial compensation for low coverage.

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 this tool is for reading the legacy Pagar.me API (V1-V4) and lists 'list_recipients' as one of the actions. The '[Flattened action: list_recipients]' line explicitly identifies the operation. It is distinguishable from sibling tools like 'pagarme_recipients_list' which likely target the newer V5 API.

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 specifies that this tool is active when the connection uses an 'ak_…' key, indicating accounts not yet migrated to V5. This provides explicit context for when to use this legacy tool over its V5 counterparts. It also lists available actions, but does not explicitly state when not to use it, hence a 4.

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