interactions_edit_followup

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

The description adds valuable behavioral context beyond the annotations: auth requirements ('token-secured (NO bot token)'), body semantics ('mirrors webhook execute body'), and return value ('{message_id, channel_id}'). This supplements the idempotentHint and readOnlyHint annotations without contradicting them.

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 extremely concise and well-structured with labeled sections (Purpose, Auth, Body, Returns). Every line adds distinct value with no filler or repetition.

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?

The description covers the essential purpose, auth, body reference, and return shape, which is helpful for a complex 11-parameter tool. However, it omits usage guidelines and detailed parameter semantics, leaving gaps that an agent must resolve by referencing webhook execute schema or sibling tools.

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 only 27%, and the description does not explain individual parameters beyond referencing 'webhook execute body'. While this hint is useful, it lacks concrete details for the 11 parameters, especially for an agent not deeply familiar with Discord's webhook execute format.

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 'Edit a follow-up message' with a specific verb and resource. It distinguishes itself from sibling tools like interactions_edit_original_response and messages_edit by explicitly targeting follow-up messages.

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 explicit usage guidance or comparison to alternatives is provided. The description does not mention when to use this tool instead of interactions_edit_original_response or webhooks_edit_message, making it hard for an agent to select between similar edit tools.

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