getCreditCardInvoice

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only says 'Detail an invoice' with no mention of side effects, permissions, return behavior, or read-only nature. This is completely absent for a likely read operation.

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 short ('Detalhar uma fatura'), but this is under-specification rather than concise efficiency. It lacks any structural elements such as context, parameter explanation, or usage notes, providing no value beyond the tool name.

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?

Despite having an output schema and two required parameters, the description gives no context on how the tool fits into the credit card invoice workflow, what the inputs mean, or what the response contains. A single vague phrase is completely inadequate for correct invocation.

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 input schema lists two required integer parameters (id and invoice_id) with no descriptions, and the description provides zero explanation of their meaning or relationship. With 0% schema coverage, the description fails entirely to compensate for the missing parameter semantics.

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 'Detalhar uma fatura' means 'Detail an invoice' in Portuguese. It identifies a verb and resource but is extremely vague, failing to specify it concerns a credit card invoice or to distinguish it from sibling tools like getCreditCardInvoices (list) and getCreditCardInvoicePayment (payment details). It essentially restates the tool name without added specificity.

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?

There is no guidance on when to use this tool versus alternatives. Closely related sibling tools (getCreditCardInvoices, getCreditCardInvoicePayment) require explicit differentiation, but the description provides none, leaving the agent to infer usage context.

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