discord_edit_webhook

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

The description only indicates 'edits,' implying mutation, but lacks details on side effects, permissions, rate limits, or idempotency. With no annotations, the description fails to disclose important behavioral traits.

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 a single sentence, but it is too short to be informative. It sacrifices clarity for brevity, making it under-specified.

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 six parameters, no schema descriptions, no annotations, and no output schema, the description is severely incomplete. It does not cover return values, errors, or the full scope of editing operations.

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?

The description does not explain any of the six parameters. Schema coverage is 0%, and the description provides no additional meaning beyond parameter names, leaving the agent without guidance on how to use fields like 'avatar', 'reason', or 'channelId'.

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 tool edits an existing webhook for Discord, distinguishing it from create, delete, and send siblings. However, it does not specify which aspects of the webhook can be edited, leaving some ambiguity.

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 is provided on when to use this tool versus alternatives like creating, deleting, or sending messages. There are no prerequisites or context for when editing is appropriate.

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