get_webhook

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

With no annotations, the description must carry the behavioral burden. It does disclose a GET/read operation via both the wording 'Get details' and the explicit endpoint '(GET /webhooks/{id})'. However, it does not mention authentication, not-found behavior, or any response shape details.

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 very short and front-loaded, with the core purpose in the first sentence and the endpoint as immediate useful context. It earns its place but is slightly under-specified compared to a more complete concise description.

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 get-by-id tool with only two parameters and no output schema, the description is adequate but not complete. It provides the operation and resource, while parameter semantics are split between description and schema, but return format and error conditions are left unspecified.

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 50%; the extraQuery parameter is well-described in the schema, while 'id' is only minimally covered. The description and endpoint add that id identifies a specific webhook, but no format or usage detail beyond that is given.

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 clearly states the action ('Get details') and resource ('a specific webhook'), and includes the endpoint path for precision. It distinguishes itself from list_webhooks through 'specific', though it does not explicitly differentiate from sibling get_webhook_event.

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 is given for when to use this tool versus alternatives such as list_webhooks or create_webhook. The description implies 'use this when you need one webhook by ID' but provides no explicit context or exclusions.

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