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

Annotations already say readOnlyHint=true and destructiveHint=false, and the description is consistent with them by stating it "opens nothing by itself." It adds genuine value beyond the annotations by disclosing the return format (step-by-step screens, buttons, fields) and the API/MCP landscape. It does not explain how the target campaign or recipient is determined.

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 action and the mechanism are front-loaded and clear, but the final sentence about Mailshake's REST API and the absence of an official MCP server is reference trivia that does not help the agent decide or invoke. The middle sentence is also a run-on combining return format and side-effect disclaimer.

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 input schema and no output schema, the description carries the burden and does explain the return shape (screens, buttons, fields). However, it never says how the specific campaign or recipient is identified when there are zero parameters, which is the main ambiguity an agent must resolve before calling.

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 this scores a 4. The description is not required to elaborate on inputs, and it correctly implies the output is self-contained instructions rather than a targeted operation.

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 ("Pause a campaign or recipient") and immediately corrects the natural misreading by saying it "Returns how to do it in Mailshake step by step ... and opens nothing by itself." An agent can tell this is a guidance tool rather than an action tool, though the name alone would mislead without that clarification.

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 a clear next step: "then do it with the cotlet_browser_* tools in the user's Mailshake Cloud Browser." That routes the agent to the correct sibling family. It stops short of explicit when-not-to-use conditions (e.g., when the agent already knows the screens), but the workflow context is unambiguous.

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