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

With no annotations, the description carries the full burden and does so well: it enumerates the three possible result values (pinned, covered_by_cluster_pin, pinned_but_archived), explains the hidden consequence for archived threads, and states idempotency explicitly. It does not cover auth/permission requirements or how to reverse the pin, which keeps it just below the top of the scale.

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?

Core purpose is front-loaded in the first sentence, followed by scoping, result semantics, and the archived caveat in a logical order with no filler. It is dense but each sentence contributes a distinct fact.

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 one-parameter mutation with no output schema and no annotations, the description supplies exactly what an agent needs: the three outcome states, the archived-thread gotcha, and idempotency. Nothing essential to calling it correctly is missing.

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?

There is a single parameter with 100% schema description coverage that already names the UUID sources (list_feed, get_cluster, search). The description adds no further meaning about the parameter, so the baseline 3 applies.

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 opens with a specific verb and resource: 'Pin one conversation to the user's Pins tab.' The word 'one' coupled with the sibling pin_cluster makes the scope unambiguous, and 'Affects Busymail only: nothing moves in the mailbox' immediately bounds what the operation does.

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?

It gives clear situational context — search returns archived conversations, so check the thread's archive state before promising visibility — and reassures that re-pinning is not an error. It stops short of explicitly naming pin_cluster as the alternative for cluster-level pinning or unpin_conversation as the reverse, leaving that to sibling inference.

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