Consultar webhook de cobranças Pix Automático

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint. The description adds that it only consults and does not alter delivery, reinforcing the read-only nature. It doesn't contradict annotations and provides operational context beyond them.

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 concise sentences, front-loaded with the action. No wasted words; each sentence provides essential information.

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 tool has no parameters, annotations cover safety, and an output schema exists, the description is complete. It tells the agent what the tool does, when to use it, and its non-destructive nature.

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 tool has zero parameters and schema coverage is 100%. Description doesn't need to explain parameters. Baseline for 0 params is 4, and the description is clear about the tool's purpose.

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 consults the current configuration of the automatic Pix charges webhook. It uses specific verb 'Consulta' and resource 'configuração vigente do webhook de cobranças Pix Automático', distinguishing it from sibling tools like pix_config_webhook_automatic_charge (which alters) and general webhook query tools.

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 explicitly says 'Use para confirmar o destino dos eventos sem alterar a entrega das notificações.' This tells the agent when to use the tool (to confirm destination) and implies when not to (when wanting to change configuration, use the sibling config tool).

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