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

The annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, and the description reinforces this in plain language: it 'opens nothing by itself' and requires a separate browser tool to effect any change. It also discloses the return content ('step by step (screens, buttons, fields)'), which the annotations cannot convey. Nothing in the text contradicts the read-only/non-destructive profile.

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 critical information (guide-only, no side effects, then use cotlet_browser_* tools) is front-loaded, which is good. However, boilerplate like 'from ChatGPT, Claude or any AI agent' adds nothing, and the trailing API inventory with a check date reads like marketing/audit filler rather than instruction. Tightening to two sentences would lose no actionable content.

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 tool with no output schema and rich annotations, the description covers what the agent needs: what it returns, that it changes nothing, and which tools complete the actual task. The only unresolved point is how this guidance-only tool relates to the emailoctopus_send_campaign / schedule_campaign siblings that the description's API note implicitly denies exist.

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 there is no parameter meaning to add and the baseline for a no-param tool applies. The description correctly does not invent any inputs, and its note that the target is the 'user's own EmailOctopus account' implicitly explains how the account context is resolved without a parameter.

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 verb+resource (duplicate a campaign in EmailOctopus) and immediately corrects the natural assumption by stating it only 'returns how to do it in EmailOctopus step by step' and 'opens nothing by itself'. That distinguishes it from the cotlet_browser_* execution tools. It falls short of a 5 only because the name/verb ('duplicate') promises an action the tool does not perform, so the agent must read the second clause to learn the tool is really a guide generator.

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 an explicit workflow: call this to get the steps, then perform the duplication with the cotlet_browser_* tools in the user's Cloud Browser. It also rules out the alternative path by stating the official API has no endpoint for creating, scheduling or sending a campaign. The one gap is that this claim sits in tension with sibling tools named emailoctopus_send_campaign and emailoctopus_schedule_campaign, which could leave the agent unsure which route is authoritative.

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