get_webhook

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

No annotations are provided, so the description must carry the behavioral burden. It discloses the HTTP method GET, which implies a read-only, non-mutating operation. However, it does not mention what happens for missing/invalid IDs, authentication requirements, or response format, leaving some behavioral uncertainty.

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 compact sentence that states the operation, the resource, and the HTTP endpoint. Every element is informative and no filler exists, making it easy to scan and action.

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 one-parameter GET tool, the description provides enough to invoke it: provide a webhook id. However, with no output schema and no annotations, it omits return value expectations, error behavior, and any caveats, so it is adequate but not fully complete.

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% and the only parameter 'id' is already described as 'The webhook id.' The description repeats 'by id' and adds the path template, but does not meaningfully expand on the parameter's semantics, such as format or source of the ID. 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?

Description states a specific action ('Retrieve'), resource ('webhook'), and key selector ('by id'), reinforced by the REST path GET /webhooks/:id. This clearly differentiates it from list_webhooks, whose purpose is fetching all webhooks, and from mutation tools like create/update/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 phrase 'by id' implies the tool is for fetching a single webhook when its ID is known, but it does not explicitly state when to prefer this over list_webhooks or mention any alternative. There is no guidance on exclusions, such as 'use list_webhooks to enumerate webhooks'.

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