Remover webhook de pagamentos de contas

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

Annotations already provide destructiveHint, readOnlyHint, and idempotentHint. The description adds the behavioral consequence that the application will stop receiving callbacks, which goes beyond the annotations but is not extensive.

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 two sentences: one stating the purpose and one stating when to use. It is concise, front-loaded, and contains no unnecessary words.

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 delete tool with one parameter and good annotations, the description provides enough context. It covers the purpose and usage scenario. It could mention idempotency or comparison with siblings, but is still adequate.

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% with descriptions for 'body' and 'url' parameters. The tool description does not add further parameter semantics, so a baseline of 3 is appropriate.

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 title 'Remover webhook de pagamentos de contas' and description 'Remove a configuração de webhook de pagamentos de contas' clearly state the verb and resource. The description also adds context about when to use, distinguishing it from sibling tools like pay_config_webhook or pay_list_webhook.

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 quando o destino não deve mais receber atualizações', providing a clear condition for usage. While it doesn't mention alternatives, the context of siblings implies it is for deletion, not configuration or listing.

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