update_batch_webhook

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

Annotations indicate not read-only, not idempotent, not destructive. The description adds authentication method, rate limit (max 10 concurrent requests), behavior in read-only/dry-run modes, and error response for invalid ID. Comprehensive but could mention idempotency implications.

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?

The description is concise yet complete, using a clear structure: purpose sentence, usage guidelines, behavioral notes, then parameter details. Every sentence earns its place without repetition.

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 the tool's complexity (3 parameters, output schema, annotations), the description covers purpose, usage, behavioral details, error handling, and parameter semantics. It is fully adequate for an agent to select and invoke correctly.

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?

With 0% schema description coverage, the description fully explains each parameter's meaning and origin: batch_webhook_id from list_batch_webhooks, url as new callback URL, account as optional with naming convention. This adds significant value beyond the bare 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 explicitly states the tool's purpose: 'Update the target URL of an existing batch webhook.' It uses a specific verb and resource, and distinguishes from siblings by referencing list_batch_webhooks and delete_batch_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?

The description clearly specifies when to use this tool ('Use to point an existing batch webhook at a new callback URL'), when not to use it (delete instead), and provides alternatives (list_batch_webhooks to find IDs, delete_batch_webhook to remove).

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