discord_unpin_message

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

The description simply restates the operation without explaining consequences, permission requirements, or state changes beyond the obvious pin being removed. It does not mention that unpinning does not delete the message, whether MANAGE_MESSAGES permission is required, or whether the action is idempotent if the message is not currently 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 a single, compact sentence with no wasted words. It is not over-written, but it is so sparse that it does little beyond restating the tool name.

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 mutation operation with no annotations, no explicit output guidance in the text, and no parameter-level descriptions, the definition is incomplete. An agent reading only the description cannot determine permission needs, the optional audit-log reason usage, or edge cases such as unpinning a message that is not pinned.

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?

The schema has four parameters, including the required channel_id and message_id plus optional reason and guild_id, but the description adds no parameter-level meaning. With essentially zero schema description coverage, the description should compensate by clarifying what each id is used for, but it does not.

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 states a concrete verb and resource: unpin a message, with the channel as the location. It is clear enough to understand the tool's basic job, but it does not explicitly differentiate itself from sibling tools like discord_pin_message or discord_delete_message, relying mostly on the tool name.

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?

There is no guidance about when to use this tool versus alternatives such as deleting a message or editing a message's contents. The intended use case is implied by the verb 'unpin,' but no contextual conditions, prerequisites, or when-not-to-use notes are provided.

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