get_webhook

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

With no annotations, the description carries the full burden: 'Get' implies a read, but it says nothing about permissions/visibility rules, what happens on an unknown or deleted webhook ID (error vs empty), or whether secret fields are redacted. For a lookup tool with zero annotation coverage, these omissions are notable.

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?

One short sentence, front-loaded with the verb and resource, with no filler. It is efficient but perhaps too terse to earn a 5.

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 with no output schema and no annotations, the description covers the core action but omits return shape and error behavior. Adequate to invoke, but not fully complete for an agent that needs to know what comes back.

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 0%, so the description is the only source of meaning for webhookId, and it only tells the agent the parameter is an identifier. It adds no format, source, or example (e.g., where to obtain the ID, whether it is the same ID returned by list_webhooks), leaving the schema's type-only declaration under-supported.

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?

States a specific verb ('Get') and resource ('a single webhook subscription') scoped by ID, which clearly separates it from list_webhooks. It does not explicitly distinguish itself from adjacent siblings like get_webhook_logs or get_webhook_secret, so it falls short of a 5.

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?

There is no explicit when-to-use guidance, no prerequisites, and no named alternatives. The 'by ID' phrasing implies it is the single-item counterpart to list_webhooks, but that routing is left entirely to inference.

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