Unpin Discord Message

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

Annotations already provide readOnlyHint=false, idempotentHint=true, destructiveHint=false. The description adds a return value but does not disclose additional behavioral traits (e.g., permission requirements, error states, or side effects).

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 short and front-loaded with the main action. However, the Args section is redundant with the schema, which is unnecessary for such a simple tool. Overall, it is efficient but could be trimmed.

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?

While the tool is simple with 2 required parameters and annotations cover safety, the description omits important context such as prerequisites (e.g., 'Manage Messages' permission), what happens if the message is not pinned, and error handling. It is minimally complete but leaves gaps.

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 100%, and the schema already fully describes both parameters with patterns and constraints. The description's Args section merely repeats the parameter names and types without adding new meaning, meeting the baseline.

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 verb 'Unpin' and the resource 'a message in a channel', distinguishing it from sibling tools like discord_pin_message (opposite) and discord_delete_message (different action).

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 implies usage for unpinning messages but does not explicitly state when to use it or when not to, nor does it mention alternatives like pin_message or delete_message. There is no guidance on prerequisites or context.

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