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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description adds genuinely new context: pinned messages become visible to the entire conversation, duration choices are 24h/7d/30d, and the call is approval-exempt yet authorized, rate-limited and logged. Only the redundant restatement of 'Idempotent' overlaps with annotations rather than extending them.

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 definition is three tight sentences and front-loads the action and its blast radius before operational notes. The 'Approval-exempt by design but fully authorized, rate-limited and logged' clause is dense but carries real information rather than padding.

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?

With an output schema present, return values need not be explained, and the description covers the things that matter for a destructive mutation: audience visibility, duration bounds, authorization, rate limiting and idempotency. The remaining gap is parameter-level guidance and preconditions, which the schema does not fill either.

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 only 33% — the 'action' enum and the 'message_id' pattern have no schema descriptions at all. The description reuses the duration values and the fact that duration is pin-only (which the schema already states for 'duration'), but adds nothing about the numeric-only message_id format or the pin-vs-unpin semantics of the action field, so it fails to compensate for the low coverage.

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 names a specific verb pair (pin/unpin) and resource (a message in its chat), so the agent knows exactly what the tool acts on. It does not explicitly distinguish itself from nearby message-mutation siblings like manage_star or manage_reaction, which keeps it just short of a 5.

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 a caution ('pin thoughtfully') but no actual when-to-use guidance: nothing says when pinning is appropriate versus starring or reacting, no prerequisite that the caller must be a participant in the chat, and no statement that unpin requires an existing pin. The agent is left to infer the selection conditions.

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