list_batch_webhooks

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

Annotations already declare readOnlyHint=true. Description adds that it returns JSON with total_items and webhooks array containing id, url, enabled. This is useful behavioral context beyond the annotation, though pagination details are omitted.

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 sentences plus a return line. First sentence states purpose, second explains concept, third provides usage guidance. No wasted words, front-loaded with key information.

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?

Returns format is explained (total_items and webhooks array) and output schema exists, reducing burden. However, the missing parameter explanation for 'account' leaves a gap in completeness. No mention of empty results or error behavior.

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?

The only parameter 'account' has no description in the schema (0% coverage) and the tool description does not explain its purpose or effect. The agent cannot determine how to use this parameter from the description.

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 'List all configured batch webhooks for the account.' The verb 'list' and resource 'batch webhooks' are specific. It distinguishes from get_batch_webhook by mentioning inspection of individual webhooks.

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?

Explicitly states 'Use to discover batch_webhook_id values' and references get_batch_webhook for detailed inspection. Provides context for when to use this tool but does not explicitly mention when not to use it.

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