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

Annotations already declare readOnlyHint=true, and the description earns credit for reconciling that with the 'send' framing by stating it 'opens nothing by itself' and only returns instructions. It also discloses the API-availability constraint that forces the browser path, which is genuinely useful behavioral context. It stops short of detailing the shape or length of the returned instructions.

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 core disclosure (returns instructions, executes nothing, use browser tools) is front-loaded and well structured. But 'from ChatGPT, Claude or any AI agent' is filler, and the trailing sentence about ProSolutions' API documentation reads as research residue rather than operational guidance.

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 parameters and no output schema, the description carries most of the burden and does state the return value (screens, buttons, fields) and the required follow-up tool family. What remains unclear is how this differs from the sibling prepare tool and whether any account preconditions apply.

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?

The tool takes zero parameters, so per the baseline there is nothing for the description to compensate for. The description does not invent parameter guidance, which is correct here.

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 names a specific resource (email campaign) and makes the unusual nature of the tool explicit: it returns a step-by-step how-to rather than performing the send. That is a real clarification over the title, which reads like an action. It does not, however, distinguish itself from the sibling paired_plus_prepare_email_campaign, which sounds nearly identical.

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 does route the agent forward ('then do it with the cotlet_browser_* tools in the user's Paired Plus Cloud Browser') and explains why (no self-serve API key), so usage context is present. What is missing is explicit when-to-use-vs-alternatives guidance, particularly against paired_plus_prepare_email_campaign and paired_plus_send_text_campaign.

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