get_webhook

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

No annotations provided; description states it returns details including delivery status and subscribed events, but lacks disclosure about idempotency, error responses, or side effects (though a read operation is implied).

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?

Two sentences, no fluff, front-loaded with action and resource. Every word earns its place.

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?

Output schema exists to explain return structure, description covers key return fields; missing failure conditions but sufficient for a simple get operation.

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 0%, so description must compensate; it adds that the parameter is 'by ID', which is minimal value beyond the schema field name 'webhook_id'.

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 clear verb 'Retrieve' and specific resource 'webhook by ID', distinguishing it from sibling tools like create_webhook (creation) and get_event (different resource).

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?

Implied usage for retrieving a specific webhook, but no explicit guidance on when to use vs alternatives (e.g., list_webhooks not available) or exclusions.

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