Consultar cobrança Pix com vencimento

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

Describes the operation as read-only ('consulta', 'sem alterá-la'), aligning with annotations (readOnlyHint, idempotentHint, openWorldHint). Adds context about retrieving revision and status, reinforcing safe behavior.

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?

Two efficient sentences with no redundancy. Front-loaded with purpose, every word serves a function.

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?

Given the presence of an output schema and annotations, the description sufficiently covers purpose and usage for a read-only query tool. No missing context.

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 coverage is 100% and describes parameters thoroughly. The description adds no extra semantics beyond the schema, just mentions 'by txid', meeting baseline.

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 the tool queries data, revision, and status of a Pix due charge by txid. It specifies the exact resource and action, distinguishing it from sibling tools that create, update, or list charges.

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?

Explicitly says to use for monitoring or display without altering, implying not for modification. Provides clear context but does not mention specific alternatives or when not to use.

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