unpin_message

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

With no annotations, the description carries the full burden of behavioral disclosure, but 'Unpin a message in a chat' only states the action without covering permissions, reversibility, idempotency, or error behavior on a non-pinned message. This is minimal and leaves important behavioral traits unspecified.

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, front-loaded sentence with no redundancy. It is appropriately sized for a simple, single-purpose operation and every word contributes to understanding.

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 simplicity of the operation and self-explanatory parameters, the description is minimally adequate for an agent to make the call. However, with no annotations, no output schema, and no usage guidance, it stops short of being fully complete for decision-making.

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, but it does not explain chat_id or message_id beyond the obvious context. While the parameter names are self-explanatory, the description adds no additional meaning about expected formats or relationships.

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 chat', so an agent can tell it performs the inverse of pin_message. It does not explicitly distinguish itself from siblings, but the action is unambiguous and specific enough for basic selection.

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 gives no guidance on when to use this tool versus alternatives like pin_message or delete_message. It also does not mention any conditions, prerequisites, or when not to use it, so the agent gets no routing hints beyond the obvious intent.

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