unpin_message

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

Annotations indicate it's a non-destructive write operation ('readOnlyHint': false, 'destructiveHint': false). The description adds minimal context beyond the action itself, but does not disclose side effects or error conditions.

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?

Extremely concise at one short sentence. No redundant words, but could be slightly expanded without harming conciseness.

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 the presence of an output schema (not shown) and simple scope, the description is minimally adequate. However, it lacks context about the effect (e.g., removes from pinned messages) and error handling.

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 0% description coverage for the only parameter 'message_id'. The tool description provides no details about what 'message_id' is or its expected format, leaving the agent with insufficient information to use it correctly.

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 'Unpin a message' clearly states the action and resource. It is specific and distinct from siblings like 'delete_message' or 'pin_message', though it could further differentiate by emphasizing it only affects pin status.

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 on when to use this tool versus alternatives (e.g., 'delete_message' or 'pin_message'). No mention of prerequisites like the message must be pinned or required permissions.

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