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

Annotations already declare destructiveHint=false and idempotentHint=true, so the safety baseline is covered. The description adds genuinely useful context beyond them: the operation is reversible via archive=false and is housekeeping rather than deletion. It doesn't add auth or rate-limit notes, but for a low-risk reversible toggle that is reasonable.

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?

Front-loads the core action in the first sentence, then adds only the unarchive flag, the id source, scope, and the explicit non-delete routing note. Every sentence earns its place with zero 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 no explanation, and the description covers the action, direction, reversibility, ID provenance, and the delete alternative. Nothing an agent needs to call this 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?

Schema description coverage is 100%, so the schema already documents all four parameters, including archive semantics and the idempotency_key contract. The description restates archive=false and the provenance of conversation_linkedin_id but adds no syntax or format detail beyond the schema. Baseline 3 when the schema carries the load.

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?

States a specific verb+resource ('Archive or unarchive a LinkedIn conversation') and immediately distinguishes itself from the sibling delete_conversation. The dual-direction behavior (archive/unarchive via archive=false) is spelled out, so the agent can tell exactly what the tool does without opening siblings.

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?

Gives clear context ('Housekeeping in the classic inbox') and names the alternative for the delete case ('Not a delete, see delete_conversation'), plus the unarchive condition. It stops short of positioning against star_conversation, the other non-destructive conversation-state sibling, so routing is not fully exhausted.

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