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

Goes well beyond the single destructiveHint annotation: it discloses idempotency semantics (updates handshake key/metadata instead of duplicating), a hard limit of 10 integrations per form, the exact return field to retain (WebHookPutResult.Hash), and the underlying endpoint (PUT /forms/{identifier}/webhooks.json). No output schema exists, and the description compensates by naming the return value.

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 'WRITE:' as a mutation marker, then packs idempotency, the limit, the return contract, and the raw endpoint into a few dense sentences. Every sentence carries operational information with no 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 4-param mutation with no output schema, the description covers everything an agent needs: safety profile, idempotency, quota, and the return value that must be stored for later deletion. Nothing material to correct invocation is missing.

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 the baseline is 3, but the description adds meaning beyond the field docs: it explains that idempotency is keyed on the URL and that handshakeKey/metadata are updated on re-invocation. The form identifier reference ('See wufoo_list_forms' in the schema) is complemented by the endpoint pattern here.

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 (adds a webhook) and resource (to a form) with the concrete effect (Wufoo POSTs every new entry to the given URL). It also distinguishes itself from the delete side of the lifecycle by noting the returned hash is needed for deletion, so an agent can tell it apart from wufoo_delete_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?

Gives clear context: idempotent per URL, so repeat calls update rather than duplicate, and the 10-integration cap constrains when it can be used. It references the downstream action (delete) but stops short of an explicit 'use X instead when...' routing statement, so it is strong context rather than full when/when-not guidance.

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