Get Webhooks

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

Since no annotations are provided, the description carries the full burden for behavioral disclosure. The verb 'Get' implies a read-only operation, and the optional archived parameter is mentioned, but there is no explicit statement about being non-destructive, pagination, or other side effects. Minimal extra value beyond what 'Get' and the schema already convey.

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 two short sentences with no filler. Every word adds meaning: 'all webhooks', 'on the account', and 'optionally include archived'. Excellent conciseness.

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 simplicity of the tool (one optional boolean parameter, no output schema, no nested objects), the description is sufficient. It states the action and the one option, which is enough for an agent to invoke correctly. A slightly richer note about return format could push to 5, but it's not necessary here.

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 coverage is 100% (the only parameter has a description). The description's mention of 'include archived webhooks' adds no meaningful information beyond the schema's own description, so baseline 3 is appropriate.

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 uses a specific verb ('Get') and clearly identifies the resource ('all webhooks on the account'), which distinguishes it from the sibling tool 'get_webhook' that retrieves a single webhook. The phrase 'on the account' adds scope clarity.

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 implies this is for listing all webhooks, with an optional flag to include archived ones. It does not explicitly mention when to use an alternative like 'get_webhook', but the context of 'all' makes the use case clear.

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