Update Webhook

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

Annotations already provide idempotentHint=true and destructiveHint=false. Description adds that update uses PATCH semantics and only changes provided fields, which is important beyond annotations. No contradictions.

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?

Two sentences + example + Spanish translation. Front-loaded with purpose and method. Slightly redundant due to bilingual text, but still efficient and scannable.

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 output schema present, description covers essential aspects: purpose, method (PATCH), partial update behavior, and usage example. No gaps given tool complexity.

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 covers 100% of parameters with descriptions, baseline 3. Description adds concrete example (id='abc123', active=false) showing how to combine parameters for a specific use case, adding practical meaning.

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?

Description clearly states 'Update an existing webhook configuration using PATCH semantics', using specific verb and resource. Distinguishes from siblings (create, delete, get, list, test) by specifying partial update rather than full creation or deletion.

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?

States 'Only provided fields change' and gives an example (disable webhook with active=false). Provides clear context for when to use (partial updates) but does not explicitly exclude alternative tools like create_webhook for full creation.

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