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

Annotations already declare destructiveHint=true, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: the receiving URL stops getting new entries immediately, and the hash cannot be rediscovered after the fact. Both are operationally important for a destructive call.

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?

Front-loads the WRITE marker and the effect, then the prerequisite, then the raw endpoint. Dense and mostly waste-free, though the literal REST path is marginally useful padding for an agent that already has the tool name.

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?

With only two fully-documented params and no output schema, the description covers what matters: mutation semantics, immediate effect, and how to obtain the required hash. Only the absence of any failure/error behavior keeps it short of complete.

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%, so both parameters are already documented in detail (form identifier formats, hash pattern). The description only restates that the hash originates from wufoo_add_webhook, which the schema also references, so it adds little beyond the 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?

States a specific verb (removes) and resource (a webhook from a form), and the 'WRITE:' prefix immediately separates it from the read-oriented siblings. It is clearly the inverse of wufoo_add_webhook, which an agent can identify without opening either schema.

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?

Gives a concrete prerequisite: the hash must come from wufoo_add_webhook, and it warns that Wufoo has no endpoint to list webhooks, which steers the agent away from searching for a list tool. It does not state explicit when-not-to-use conditions, but the routing context is clear.

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