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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description aligns with that by presenting a query-only operation. It adds the list of possible statuses and batch support, but it does not disclose any additional behaviors such as error conditions, response format, or account-scoping semantics. No contradiction exists between description and 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 compact: one core sentence, a list of status values, and a single bulk-support sentence. It is front-loaded with the primary query key and avoids filler, making it easy for an agent to parse quickly.

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 status tool with one required parameter and no output schema, the description covers the main query key, the statuses, and batch behavior. The mostly clear gap is the `account` parameter, but overall the tool context is sufficient for a human or agent to invoke it 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?

With 0% schema description coverage, the description does some of the work by clarifying `transaction_id` as the query key and `transaction_ids` as useful for batch execution. However, `account` is left undocumented, and no constraints or relationship between the parameters are described, leaving a noticeable gap.

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 explicitly states the specific action: 'Consulta o status atual' (query the current status) of a Pix charge by `transaction_id`. It differentiates the tool from sibling status tools such as `paghiper_get_boleto_status` by naming Pix, and it enumerates the possible statuses, further clarifying its purpose.

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 makes clear that this tool is for checking live Pix statuses and mentions bulk behavior via `transaction_ids`, which gives useful usage context. It does not explicitly contrast with alternative tools like `paghiper_list_transactions` or `paghiper_get_boleto_status`, but the Pix-specific purpose is clear enough for selection.

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