Unpin message

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

Annotations already declare readOnlyHint=false and destructiveHint=false. The description adds the behavioral note that the message content is not affected, which aligns with destructiveHint=false. However, it does not disclose any additional behaviors such as permissions needed, error conditions, or whether the message must already be pinned.

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 with two short sentences, conveying the core action and a key clarification without redundancy.

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?

For a simple unpin operation, the description is mostly adequate but lacks context about required message_id semantics, the need for the message to be pinned, and any permission requirements. The tool's input schema and annotations are limited, so more detail would improve completeness.

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 50% (only guild and channel have descriptions). The description contains no parameter information, leaving message_id and reason unexplained. The agent must infer that message_id identifies the pinned message and reason is for audit logging, which is not clarified.

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 action ('Unpin a message') and the resource ('message'), and explicitly differentiates from deletion with 'The message itself is untouched.' This distinguishes it from delete_message and clarifies its scope.

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 does not name alternative tools or explicit when/when-not conditions, but the phrase 'message itself is untouched' gives contextual guidance that this tool is for removing a pin without deleting content. It implies use when the goal is to reverse a pin, but no exclusions are provided.

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