discord_get_webhook

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

The description carries the behavioral disclosure burden because no annotations are provided. It conveys that this is a retrieval operation and explicitly warns that tokens are never returned, which is valuable context an agent would not have inferred from the schema alone.

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 two short sentences with no filler. The main purpose is front-loaded, and the token caveat is a concise, meaningful addition.

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 simple lookup tool with an output schema, the description is mostly adequate but leaves gaps: it does not explain the optional guild_id parameter and does not provide routing guidance relative to list_webhooks. The absence of annotations increases the need for fuller context.

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 needed to explain webhook_id and guild_id, but it does not. The field names and titles provide minimal hints, and the optional guild_id's purpose is entirely undocumented.

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 the purpose: retrieve webhook metadata for a webhook. It adds a useful distinguishing note about tokens never being returned, but it does not explicitly contrast itself with discord_list_webhooks or state that it operates on a single webhook by ID.

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 guidance on when to use this tool versus siblings like discord_list_webhooks, discord_create_webhook, or discord_edit_webhook. The intended context must be inferred from the tool name and schema rather than being explicitly stated.

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