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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds one useful behavioral consequence beyond annotations: 'Pending emails stop.' However, it does not clarify whether the lead is archived or permanently deleted, whether recovery is possible, or what permissions are needed.

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?

Two short sentences with zero wasted words, and the action is front-loaded before the consequence. It is appropriately terse for a simple single-parameter tool.

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 destructive mutation with one required parameter and no output schema, the description covers the basic action and one side effect. It is minimally adequate but leaves important gaps: recoverability, exact removal semantics, and how to source the required leadId.

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 should compensate for the single required leadId parameter, but it does not mention the parameter at all. The schema provides type/format/pattern for leadId but no semantic guidance about where to obtain the lead ID, such as from soclo_leads_list.

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 states a specific verb and resource: 'Remove a lead from the list.' That is clearer than the tool name 'archive' alone and tells the agent the core action. It does not distinguish this from sibling operations like suppress, reject, or outcome, leaving ambiguity about which removal semantic applies.

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 no guidance on when to use this tool versus alternatives such as soclo_leads_suppress, soclo_leads_reject, or soclo_leads_outcome. The description gives no prerequisites, exclusions, or confirmation steps before a destructive removal.

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