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

Beyond annotations (destructiveHint=true), the description discloses that the tool queues rather than delivers, puts a confirmation dialog in front of the user, refuses on mismatch, and instructs to stop if the user declines. This provides significant behavioral detail beyond the annotation flags.

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?

The description is a single dense paragraph but every sentence adds value, covering safety, confirmation requirements, and error behavior. While it could be broken into bullets for readability, it is not redundant or padded.

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?

Given the safety-critical nature and lack of an output schema, the description covers what the tool does, when to use it, failure modes (mismatch, user decline), and the queuing behavior. It does not explicitly state the success return value, but that is less critical for an action tool with clear side effects.

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 descriptions for all three parameters are present and meaningful: leadId is sourced from list_pending_outreach, confirmName proves the intended recipient, and confirmText requires verbatim user-approved text. The tool description further explains why these confirmations are needed, adding context beyond the schema.

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 clearly states the tool 'Queue an approved outreach draft for sending to a real person on LinkedIn.' It specifies the action (queueing/sending), the resource (outreach draft, person), and distinguishes it from siblings like rewrite_outreach and list_pending_outreach by emphasizing 'approved' and 'queue.'

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 provides usage context: leadId comes from list_pending_outreach, and the tool requires explicit user confirmation. It also gives alternative guidance by instructing to 're-read it with list_pending_outreach' on mismatch. However, it does not explicitly contrast with all sibling tools (e.g., continue_campaign), though the purpose is clear enough.

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