Retrieve a webhook

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint, which cover safety and idempotency. The description adds the API endpoint (GET /webhooks/{webhookId}), which gives a bit more detail, but it does not disclose other behavioral aspects like response format, error handling, or rate limits.

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 concise with only two sentences. It front-loads the purpose and includes the API call detail efficiently. No redundant or unnecessary words. However, it could be slightly more informative without increasing length significantly.

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?

Given the low complexity (single parameter, no output schema), the description is minimally complete: it identifies the resource and action. However, it lacks context on when to use this tool over similar retrieval tools (like render_retrieve_deploy) or how to interpret the result, which may leave some gaps for an AI agent.

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 100%, so the schema fully documents the required parameter. The description reiterates 'with the provided ID' but does not add any new meaning or clarify the parameter beyond what the schema already provides (type, pattern, example).

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 'Retrieve a webhook' and specifies retrieving by ID, leaving little ambiguity about its function. However, it does not explicitly differentiate itself from sibling tools like render_list_webhooks or render_delete_webhook, which could cause confusion about when to use this specific tool.

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 description implies usage when you have a webhook ID, but it does not provide explicit guidance on when to use this tool versus alternatives (e.g., listing webhooks for ID discovery, or using update/delete for mutations). No when-not or exclusion criteria are mentioned.

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