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

With no annotations, the description still discloses the important side effects: AI messaging is stopped, pending auto-replies are cancelled, and no message is sent. It does not cover permissions, reversibility, or how to hand the contact back to the AI, leaving some behavioral gaps for a mutation tool.

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?

One compact sentence with the action front-loaded, the ID source in parentheses, and side effects at the end. Every phrase adds information; there is no filler.

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 one-parameter mutation with no annotations or output schema, the description supplies the action, the input source, and the key outcomes. It is nearly complete, but could state whether the takeover is reversible or what the caller should expect afterward.

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 0%, so the description must carry the parameter meaning; it does by specifying that outreach_id comes from list_campaign_linkedin_outreach or list_linkedin_conversations. It stops short of documenting the exact ID format or field name in those responses.

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 gives a specific verb ('Stop...messaging') and a precisely scoped resource ('this LinkedIn contact'), and the parenthetical names the two list tools that supply the outreach id. An agent can distinguish this contact-level takeover from message-sending or campaign-thread tools.

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?

It makes the use case clear—stop AI outreach for a contact—and identifies where the required outreach_id comes from, which is the key prerequisite. It does not explicitly compare with siblings such as takeover_campaign_thread or send_linkedin_message, so it lacks full alternative/exclusion guidance.

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