discord_message

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It fails to mention that delete is destructive, that dryRun defaults to true, that confirm is required, or any side effects, reversibility, or permission specifics beyond 'allowed.' This is a significant gap for a mutation tool.

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 concise sentence, front-loaded with all five actions. It contains no redundant words and is immediately scannable. While under-specification is a problem, that is addressed in other dimensions.

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 8 parameters, 5 possible actions, no annotations, and no output schema, this one-line description is grossly incomplete. It does not indicate required fields per action, safety mechanisms like dry-run, confirmation steps, or behavior in failure scenarios.

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 must compensate for the lack of parameter documentation. It does not explain dryRun, confirm, reason, content, or messageId, nor which parameters are required for each action. The only implied meaning is the 'action' enum, which is already in the 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?

The description clearly identifies the tool as handling message operations (send, edit, delete, pin, unpin) in a guild channel. This is a specific verb+resource combination that distinguishes it from sibling tools like discord_list_messages (read-only) and discord_upsert_channel (channel management).

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 or when not to use it. The phrase 'allowed guild channel' hints at permissions but does not constitute explicit usage guidelines. Sibling tools are not mentioned.

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