webhooks_get

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

Beyond the annotations (readOnlyHint=true, idempotentHint=true), the description discloses critical behavioral quirks: the bot-auth path strips the token from the response, and `name` is raw creator-controlled data with `untrusted_name` as a fenced copy. This adds substantial context for the agent.

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 well-structured with clear sections (Purpose, When to use, Asymmetry, Returns) and every sentence adds value. It is concise yet dense with useful information, front-loading the purpose.

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?

Despite having an output schema, the description provides essential contextual details about the response (token stripped, untrusted_name) and explains the key asymmetry with the token-bearing endpoint. This is complete for a simple read 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 coverage is 100% with a clear description ('Webhook to fetch') and a pattern for the ID. The description does not add additional meaning beyond the schema, so the baseline of 3 is appropriate.

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 states 'Get a webhook by id' with a specific verb and resource, and explicitly distinguishes itself from `webhooks_get_with_token` by noting the difference in token handling. This clearly differentiates it from its sibling 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 explicitly states when to use this tool ('Inspect a webhook you discovered via webhooks_list_channel or webhooks_list_guild') and provides a clear alternative ('Use webhooks_get_with_token when you already hold the token and want the freshest record'). This is excellent guidance.

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