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

The crucial behavioral fact is disclosed: the tool 'opens nothing by itself' and returns screen/button/field instructions, which explains and reinforces the readOnlyHint=true annotation rather than contradicting it. This is meaningful value beyond the annotation. It does not address auth requirements, failure modes if the user's Privy UI differs, or the shape/length of the returned guide.

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 clarification (returns instructions, opens nothing) is well placed early, but the phrasing is padded — 'from ChatGPT, Claude or any AI agent' adds nothing, and the closing API/dating sentence reads as an aside whose relevance is only implied. It could be one tight sentence shorter without losing information.

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 the burden of explaining the return value, and it does so (step-by-step screens, buttons, fields) plus the required handoff to browser tools. Adequate for the tool's complexity, though it omits what an agent should do if the guide's steps do not match the user's Privy UI.

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 semantics to compensate for; the 4 baseline applies. The description correctly implies all campaign details are supplied later through the browser tools, but does not explicitly say so, leaving a small ambiguity about where the campaign content comes from.

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 the resource (email campaign in the user's own Privy account) and then corrects the misleading verb by clarifying that the tool returns step-by-step Privy instructions rather than creating anything. It names the follow-up tool family (cotlet_browser_*) so the agent can distinguish it from the browser actions, but it never contrasts itself with the adjacent privy_* campaign tools like privy_send_or_schedule_campaign or privy_duplicate_campaign.

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?

Clear usage context: call this to get the recipe, then execute it with cotlet_browser_* in the user's Privy Cloud Browser. The closing note about Privy's paid public API and read-only MCP server implicitly explains why a guide-based tool is needed. It stops short of explicit when-not conditions or directing the agent to a specific sibling when an API path exists.

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