Webhooks_Retrieveawebhook

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

No annotations provided, so description bears full burden. Only states 'Retrieve', implying read-only and non-destructive. No disclosure of authentication needs, error behavior when webhook not found, rate limits, or response format.

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 (3 words) but lacks detail, bordering on under-specification. Every word is relevant but does not add value beyond the tool name. Could be considered too terse for effective agent use.

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 no output schema, 2 optional params with vague descriptions, and no annotations, the description is insufficient. Missing clarification on required identifier (if any), return type, and how this differs from listing webhooks. Incomplete for a retrieval tool.

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% (both parameters documented in schema as 'Query parameter: ...'). Description adds no additional meaning beyond what schema provides. Baseline 3 is appropriate as schema already covers parameter names and types.

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 specific verb 'Retrieve' and resource 'webhook', clearly indicating a read operation. However, it does not differentiate from the sibling 'Webhooks_Listallwebhooks' which also retrieves webhooks but in a list. No mention of retrieval by ID or other criteria.

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 on when to use this tool versus alternatives like list, create, update, delete webhooks. No prerequisites mentioned (e.g., need a webhook ID). The tool name implies retrieving a single webhook but the schema lacks an ID parameter, causing confusion.

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