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

Annotations declare destructiveHint=true and openWorldHint=true, so the bar is lower, yet the description adds the crucial nuance that drafting does not send anything pending approval. It also explains the clientRequestId retry semantics ('never charged twice'). It omits what is actually consumed/charged (credits) beyond the retry note.

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 short sentences, none wasted. The deliverable comes first, the approval safeguard second, the retry hint last — a sensible front-loaded order.

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 no output schema, the description usefully implies the output (email and LinkedIn drafts) and the gate before sending. It does not say what the call returns (draft ids, status) or how the drafts are retrieved/reviewed afterward, which leaves a small gap for an agent planning the next step.

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 coverage is 75%: credits and pricingVersion are self-documented as 'from the matching quote' and clientRequestId's retry rule is restated. leadId carries no description in either place, and the description only implies it via 'for one lead'. Baseline 3 is appropriate.

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 and resource: writes a first email, two follow-ups and LinkedIn notes for one lead. The deliverable set is enumerated, so an agent knows exactly what it produces and can distinguish it from soclo_leads_draft_quote, which only prices the work.

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 an explicit precondition ('after the owner has seen the quote') that routes the agent to draft_quote first, and signals the follow-on approval step ('nothing is sent until the owner approves'). It stops short of naming soclo_leads_approve or stating when not to use this tool.

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