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

No annotations are provided, so the description carries the burden of behavioral disclosure. It does convey that this is a read operation returning configuration details (URL, method, headers, status), but it does not mention auth requirements, error behavior, or whether the webhook must exist. This is adequate but not rich.

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 compact and front-loaded with the primary action, followed by a concise 'Use when' list. Every sentence earns its place, and there is no redundant filler.

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 simple by-ID retrieval tool with two fully documented parameters and an output schema, the description is adequate. It names the key output concepts and when to use it. It could add a note about authentication fallback or non-existent webhook behavior, but these are minor gaps given the tool's simplicity.

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 the parameters are already fully documented. The description adds only the contextual point that retrieval is by webhook ID, which does not significantly extend the schema meaning. 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 ('Retrieve'), names the resource ('full configuration of a specific webhook'), and clarifies it is identified by 'webhook_id.' This distinguishes it from list_webhooks or get_webhook_history without needing to open the schema.

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 'Use when' block gives a clear trigger: inspecting a webhook's URL, method, headers, or status by ID. It does not explicitly name alternative tools to avoid, but the by-ID qualifier and the mention of configuration details imply when this tool is the right choice versus listing or history tools.

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