obter_status_pix

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

With no annotations provided, the description carries the full transparency burden. It only says 'Consulta' (query), implying a read operation, but does not disclose side effects, required identifier behavior, return format, or limitations. Significant behavioral context is missing.

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 a single, clear, front-loaded sentence with no redundant words. It is appropriately concise for a simple query tool, though it could include a bit more useful context without becoming verbose.

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 no annotations, no output schema, and three undocumented optional parameters, the description is incomplete. It defines the tool's purpose well but fails to provide enough contextual guidance on parameter usage, return expectations, or how it relates to sibling tools.

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% and the description provides no meaning for the three optional parameters (id_pix, codigo_titulo, codigo_integracao). The agent is left without guidance on how these parameters identify a specific PIX charge or whether at least one is required.

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 specific action ('Consulta' = query) and resource ('status de uma cobrança PIX específica' = status of a specific PIX charge), and the word 'apenas' (only) differentiates it from sibling tools that retrieve full PIX details or list statuses.

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 implies this tool is for checking the status of a single PIX charge, but it does not explicitly mention alternatives or when not to use it. The 'apenas' provides some constraint but no direct comparison to obter_pix or listar_status_pix.

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