Update Webhook

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

Adds detail beyond annotations by confirming partial update and listing modifiable fields. No contradiction with annotations (destructiveHint, idempotentHint).

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 efficient sentences, front-loaded with action and then specifics, no unnecessary words.

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 moderate complexity, annotations, and presence of output schema, the description captures core partial update behavior but could explain optional org_uuid and request_id usage.

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?

Description covers 4 of 7 parameters (name, url, enabled, event_types) despite 0% schema coverage, adding meaningful context for those fields, but omits webhook_id, org_uuid, and request_id.

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?

Clearly states action 'update' on resource 'existing Automox webhook', lists updatable fields, and distinguishes from sibling tools like create_webhook or 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?

Specifies partial update behavior ('only provided fields are changed'), providing context for use, but does not explicitly mention prerequisites or alternatives.

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