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 bulk support context but does not disclose additional behavioral traits such as authentication requirements, rate limits, or side effects.

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 reasonably concise but mixes Portuguese and English, and the structure (list of actions, then mention of bulk) could be cleaner. It is functional but not optimally front-loaded.

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 tool with 6 parameters and no output schema, the description covers the main actions and bulk support but lacks details on return format, error handling, and the account parameter. Annotations provide a safety profile, so completeness is moderate.

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?

With 0% schema description coverage, the description provides some meaning for parameters: it mentions 'data' can contain subscription_id, customer_id, status, due_since/until; page and size for pagination; invoice_id and invoice_ids. However, the 'account' parameter is not explained, and 'data' is ambiguously typed as a string.

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 that the tool is for invoices (faturas) in Pagar.me V5 and enumerates two actions: list and get. It also mentions bulk support, which differentiates it from a simple get. However, it does not explicitly distinguish itself from the sibling pagarme_invoices_list, which might be confusing.

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?

No guidance is provided on when to use this tool versus alternatives like pagarme_invoices_list or pagarme_invoices_cancel. The description does not specify contexts for list vs get vs bulk operations.

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