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

The description adds substantial behavioral context beyond the idempotentHint annotation: it states admin scope is required, cost is free, returns {deleted: true}, and enumerates possible errors including not_found when no webhook is registered. This clarifies edge cases like repeated deletions and rate-limiting. No contradiction with 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 extremely compact and well-structured, segmented into Args, Cost, Returns, and Errors. Every sentence earns its place and there is no redundant filler.

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 one-parameter delete tool, the description covers prerequisites, cost, return value, and all relevant error conditions. It even clarifies idempotency behavior by noting that deleting a non-existent webhook yields not_found, which is important for repeated calls. The output schema exists, and the description is complete enough for an agent to invoke 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?

The schema already provides detailed fallback semantics for api_key with 100% coverage, so the baseline is 3. The description adds the requirement that the key must have admin scope, which is additional meaning not present in the schema, elevating it to 4.

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 uses the specific verb 'Remove' and identifies the resource as 'this account's webhook,' clearly distinguishing it from sibling tools like set_webhook, get_webhook, or delete_account. The '(WP-M)' is slightly cryptic but does not obscure the 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 implies the tool is for deleting the account webhook and notes the admin scope prerequisite, but it does not explicitly discuss when to use it relative to alternatives or provide any exclusions. It would benefit from mentioning that set_webhook is for creation/updating.

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