unpin_message

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

Annotations already indicate this is a write operation (readOnly=false) and not idempotent. The description adds the key behavior of unpinning all when message_id is None, which is useful context. However, it does not disclose potential side effects, error conditions, or permission requirements, so it doesn't go far beyond the annotations.

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 a brief one-line purpose followed by an args block. Every sentence adds essential information, with no filler or 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 tool with two parameters, the description adequately explains the main behavior. An output schema exists, so return values are covered there. It could add more about edge cases (e.g., no pinned messages) but is sufficient for typical usage.

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. It does explain the message_id parameter and its None meaning, but it does not clarify the 'chat' parameter at all. Since there are 2 parameters and only one is explained, the compensation is partial.

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?

Description clearly states the tool unpins one or all pinned messages in a chat, using a specific verb and resource. It distinguishes itself from the sibling tool pin_message by explicitly covering the 'unpin' 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 provides clear guidance on when to use each mode: if message_id is specified, unpin that message; if None, unpin all pinned messages. It doesn't explicitly mention alternatives or exclusions, but the context is sufficiently clear for a single-purpose tool.

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