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

With readOnlyHint=true and destructiveHint=false already declared, the description usefully confirms the tool performs no action itself and only returns procedural guidance. It also notes Privy's public API availability (paid plans) and a read-only MCP server, which is helpful context. It does not disclose response shape beyond 'step by step', size, or freshness of the 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 clarification ('returns how to do it step by step... opens nothing by itself') is front-loaded and valuable. The 'from ChatGPT, Claude or any AI agent' clause is filler, and the trailing sentence about Privy's official API is tangential and dated-checking noise.

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, read-only guide tool with no output schema, the description covers what most agents need: that the output is procedural instructions and that execution happens via the browser tools. It leaves unstated whether the guide is generic or account-specific, which is the main residual gap.

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?

Zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description does not explain how the guide knows which campaign or account is targeted, but with no inputs that is inherent to the design.

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 states a specific capability: it returns step-by-step Privy instructions (screens, buttons, fields) for sending or scheduling a campaign, and explicitly says it 'opens nothing by itself.' That resolves the ambiguity in the name, which sounds like a write action. It does not, however, distinguish itself from sibling Privy tools such as privy_create_email_campaign or privy_launch_display.

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 clear sequencing guidance — call this first to get the steps, then execute with the cotlet_browser_* tools in the user's Privy Cloud Browser. It also implies a when-not ('opens nothing by itself'). What's missing is guidance on when to prefer this over the sibling privy_* action tools or Privy's own public API, which it only mentions.

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