update_webhook

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

Describes partial update behavior and return value. Given no annotations, the description carries the burden and does well, though lacks explicit mention of permissions or side effects. Still, it is transparent about the non-destructive pause option.

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?

Three short sentences, each serving a distinct purpose: purpose, behavior, usage tip, return value. No filler. Front-loaded with key info.

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?

Given no output schema, the return value mention is sufficient. Parameter count is covered. Sibling tools are differentiated. The description is self-contained and complete for the tool's 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. The description adds value by explaining partial update semantics and the inactive status use case, going 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 description clearly states the verb 'Update' and the resource 'webhook', listing specific updatables (endpoint URL, subscribed events, active status). It distinguishes from siblings like create_webhook and delete_webhook by focusing on modifications.

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?

Provides clear context: only provided fields change. Offers a specific usage tip for pausing without deleting via status: 'inactive'. Does not explicitly exclude other scenarios, but context is sufficient.

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