discord_edit_webhook

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

Annotations already provide destructiveness and idempotency hints. Description adds context on permission requirement and partial update semantics, consistent with annotations. No contradiction.

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 sentences; first conveys purpose and scope, second adds constraints and return info. No redundant words, highly efficient.

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?

No output schema, but description mentions 'Returns a confirmation'. Covers key behavioral aspects: partial update, permission, return. Sufficient for a simple mutation 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 covers 100% of parameters with descriptions. Description adds value by clarifying that only provided fields are updated (partial update semantics), which is not explicit in schema.

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 clearly states verb 'Update' and resource 'webhook', lists specific changeable attributes (name, avatar, channel). Distinguishes from sibling tools like delete or create webhook.

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?

Specifies partial update behavior ('Only provided fields change') and required permission ('Manage Webhooks'). Does not explicitly mention when not to use, but context is adequate for a simple mutation tool.

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