list_all_webhooks

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

Warns about pagination with ⚠️, which is helpful. However, no annotations exist, and the description does not mention that the tool is read-only, authentication requirements, rate limits, or behavior when no webhooks exist. Partial disclosure.

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, front-loaded with warning and purpose. Efficient, though the second sentence is slightly generic. No filler content.

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 and no annotations, the description fails to explain return format, whether it lists full details or just metadata, and does not set expectations for the response. Adequate but not fully complete for an AI agent.

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 description coverage is 100%, so parameters are documented in schema. The tool description adds no extra meaning about parameters, not even explaining the required schema_file parameter or how cursor/limit interact for pagination. No added value over 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?

Description clearly states the tool retrieves a list of existing webhooks for the current account, with a specific verb 'retrieve' and resource. Distinguishes from siblings like webhook_details which gets a single 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?

No guidance on when to use this tool versus alternatives such as webhook_details, create_account_webhook, or other list tools. Does not specify context or exclusions.

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