Get Webhook

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

No annotations are provided, so the description carries the behavioral burden. It clearly indicates a read-only lookup ('Get details'), but it does not disclose auth requirements, not-found behavior, or what 'details' actually includes. This is adequate for a simple get operation but provides no extra behavioral context.

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 a single, efficient sentence with no filler. The verb, resource, and lookup criterion are all present and front-loaded.

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?

For a single-parameter read operation, the description is nearly complete. The only gap is that with no output schema, 'details' is somewhat vague about the return shape, but the low complexity makes additional guidance unnecessary.

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%, with the schema already describing webhookId as 'The ID of the webhook'. The description only alludes to this parameter with 'by ID' and adds no additional format, source, or constraint information.

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 uses a specific verb ('Get'), a clear resource ('a webhook'), and a precise lookup key ('by ID'). This cleanly separates it from sibling tools like create_webhook, update_webhook, and 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?

The retrieval intent is implied by 'Get details' and the single-ID signature, so an agent can infer it is for fetching an existing webhook. However, the description does not explicitly state when to prefer this tool over alternatives or mention any prerequisites or error conditions.

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