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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds one useful behavioral trait: bulk execution through credit_card_ids. However, it does not disclose return format, pagination, or how start_date and end_date affect the result, so the added behavioral context is modest.

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 extremely concise: two short sentences that front-load the purpose, then state the required parameter and the bulk option. Every sentence earns its place and there is no filler.

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, read-only list operation, the core invocation is clear: provide credit_card_id and optionally use batch ids. But the description lacks return-value details, omits start_date/end_date semantics, and gives no guidance about the closely related singular sibling, leaving some context incomplete.

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 description coverage is 0%, so the description must compensate. It explains credit_card_id as required and credit_card_ids as a bulk alternative, but start_date and end_date are left completely undocumented in both the schema and the description, leaving their meaning and expected format unclear.

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 opens with 'Lista faturas de um cartão', a specific verb+resource statement, and identifies the required credit_card_id. The tool's purpose is clear, but it does not explicitly differentiate itself from the closely related sibling organizze_get_credit_card_invoice, relying on the plural 'faturas' and the tool name to make that distinction.

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 provides a clear prerequisite ('Informe credit_card_id') and highlights bulk support via credit_card_ids, so the agent knows how to invoke it. However, it does not explain when to choose this tool over the singular invoice sibling or give explicit when-not-to-use guidance.

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