discord_fetch_webhook_message

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds that it fetches a single message with specific return fields and requires the webhook token. This provides useful behavioral context beyond annotations, though it doesn't mention rate limits or failure scenarios.

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 concise sentences with no wasted words. The description efficiently communicates purpose, input requirements, and output scope.

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 tool's simplicity, the description covers purpose, parameters, output (fields listed), and prerequisites. With an output schema present, the description is complete enough for proper selection and invocation.

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 clear parameter descriptions. The description adds that the webhook must have sent the message and requires the secret token, which reinforces authentication needs but does not significantly extend schema information. Baseline 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 clearly states 'Fetch a single message sent through a webhook' with specific fields returned (id, content, embed count, timestamp). It distinguishes this tool from siblings like `discord_fetch_pinned_messages` or `discord_read_messages` by explicitly mentioning webhook context.

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 mentions it is read-only and requires the original webhook token, providing clear prerequisites. However, it does not explicitly state when to use versus alternative tools like `discord_read_messages` for non-webhook messages, though the context is implied.

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