Update webhook

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered elsewhere. The description adds nothing beyond that: it never says whether attributes is a partial merge or full replacement, what the secret replacement does, or that confirm gates the action.

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?

A single short sentence with no wasted words, but the brevity reflects under-specification rather than efficiency. It is front-loaded with the verb, which is the one positive structural trait.

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 destructive mutation tool with 8 parameters, a nested payload object, a mutually exclusive payload_file path, and no output schema, this description leaves the agent without the operating rules it needs. Annotations cover the safety hint but not the invocation contract.

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 75%, so most fields are documented structurally, but the description still only echoes 'ID and provided attributes' without explaining the payload vs payload_file vs body-flags exclusivity, the confirm gate, or the account scoping semantics. It adds no meaning beyond the schema.

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 sentence restates the tool name ('Update webhook') plus a generic clause ('with the given ID and provided attributes') that adds no scope or distinguishing detail. It does not differentiate from create_webhook, delete_webhook, or get_webhook beyond the obvious verb.

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?

There is no guidance on when to use this versus create_webhook/delete_webhook, no mention of prerequisites (e.g., the confirm flag or account scoping), and no indication of when not to use it. Nothing in the text helps an agent choose this tool over a sibling.

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