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

Goes well beyond the sparse destructiveHint annotation: discloses idempotency semantics (same URL updates handshake key/metadata rather than duplicating), the 10-integration quota, the returned WebHookPutResult.Hash and why to retain it, and the underlying API endpoint. This is exactly the mutation-behavior context an agent needs.

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?

Four dense sentences, front-loaded with the WRITE marker and the core action; each sentence (idempotency, quota, return value, endpoint) carries distinct 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?

With no output schema, the description compensates by naming the returned field and its downstream use; it also covers quota limits, idempotency, and the API route. Nothing material is missing for correct invocation.

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 description coverage is 100%, so both required and optional parameters are already documented in the schema. The description's mention of the handshake key and metadata setting is consistent with the schema but adds little new syntax or format detail, so the baseline 3 applies.

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?

Opens with 'WRITE: adds a webhook to a form' — a specific verb plus resource — and explains the effect (Wufoo POSTs every new entry to the given URL). This clearly separates it from sibling wufoo_delete_webhook and the read-oriented list/get 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?

Explains the triggering behavior and the idempotency rule so an agent knows re-calling with the same URL is safe, plus the hard cap of 10 integrations per form. It stops short of explicitly naming delete_webhook as the alternative operation, though it alludes to needing the returned hash to delete.

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