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

Annotations already provide readOnlyHint=false, destructiveHint=false, and idempotentHint=true, so the bar for additional disclosure is lower. The description contributes the reversible-toggle nuance (archive=false to unarchive), which is beyond the annotations. It does not disclose permission requirements, rate limits, or state-dependent behavior, but the annotation coverage keeps this at an acceptable mid-level.

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?

Three concise, front-loaded sentences cover the operation, the toggle behavior, and where the ID comes from. No redundant filler or restatement of schema properties that are already fully described.

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 4-parameter toggle with a full output schema and rich annotations, the description communicates the core reversibility and the source of the thread ID. It lacks a worked example or edge-case notes, but the tool's low complexity and the presence of the output schema make this adequately complete.

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 all four parameters are already adequately documented. The description repeats the schema's meaning by saying archive=false reverses the action and conversation_linkedin_id comes from list_conversations, but it adds little beyond the schema, so the baseline score 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?

Description clearly states the verb and resource ('Archive or unarchive a LinkedIn conversation') and distinguishes the operation in principle from siblings like delete_conversation and star_conversation. It does not explicitly name those alternatives, so it falls just short of full 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?

The description offers operational guidance: set archive=false to unarchive and source conversation_linkedin_id from list_conversations. It never says when archiving should be chosen over deleting, starring, or other conversation actions, leaving usage timing implied rather than explicit.

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