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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, and the text is consistent with them: 'opens nothing by itself'. Beyond the annotations, it explains the return content (step-by-step screens, buttons, fields) and records an API-coverage finding with a verification date, which is genuinely useful behavioral context. It does not say how large or structured that step-by-step output is, or what happens if the account has no campaign to schedule.

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 key routing fact ('opens nothing by itself; then use cotlet_browser_*') is front-loaded and earns its place, but the opening clause restates the title, and 'from ChatGPT, Claude or any AI agent' is filler that adds no decision value. The final API-inventory sentence is long and only partially relevant to invoking this tool.

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 zero-parameter guidance tool with no output schema, the description covers what it returns and how to act on that return, which is the essential loop. What is missing is prerequisite state: it never says a campaign must already exist or how to get to the scheduling screen from a cold start, which matters for an agent planning a multi-step browser flow.

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 and the schema is fully closed (additionalProperties: false), so there is nothing for the description to disambiguate. Baseline 4 applies. The description correctly implies no arguments are needed and that account context comes from the browser session rather than from inputs.

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 makes clear that this tool does not schedule anything itself: it returns a step-by-step how-to ('screens, buttons, fields') and the actual work happens through the cotlet_browser_* tools. That is a specific and unusual capability, and it is stated plainly. It loses a point because the name/title ('schedule_campaign') reads like a write action, and the description does not explicitly contrast itself with emailoctopus_send_campaign or emailoctopus_list_campaigns.

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 gives a concrete follow-on path ('then do it with the cotlet_browser_* tools in the user's EmailOctopus Cloud Browser'), which is exactly the context an agent needs to chain calls. It also justifies why this route exists (no v2 API for creating, scheduling, or sending a campaign). It stops short of stating when a sibling such as emailoctopus_send_campaign is the better choice, or what prerequisite state (an existing draft campaign) the user must be in.

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