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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered; the description nonetheless adds the key behavioral fact that it "opens nothing by itself" and specifies the return content (screens, buttons, fields). Since no output schema exists, that disclosure of return shape is genuinely valuable beyond the structured fields.

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 purpose and the return content are front-loaded in the first two sentences, which is good, but the trailing sentence about Privy's paid-plan API and a read-only MCP server "(checked 23 Oct 2026)" is background trivia with a timestamp that adds little for an agent deciding how to call the 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?

With zero parameters, no output schema and annotations covering safety, the remaining burden is telling the agent what comes back and what to do next, and the description does both (step-by-step screens/buttons/fields, then cotlet_browser_* tools). The only gap is that the name/behavior mismatch is stated rather than resolved.

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 (empty object, additionalProperties false), so there is no parameter meaning to convey and the baseline for a parameterless tool applies. Nothing in the description contradicts or muddies the schema.

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 opening sentence states a specific verb and resource ("List campaigns in the user's own Privy account"), but the second sentence reverses the framing: the tool actually "Returns how to do it in Privy step by step (screens, buttons, fields) and opens nothing by itself." The internal tension between "lists campaigns" and "returns instructions for listing campaigns" leaves the agent unsure whether campaign data or a procedure comes back.

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 follow-on path: use this to get the steps, "then do it with the cotlet_browser_* tools in the user's Privy Cloud Browser," which correctly routes the agent away from expecting this tool to perform the action. It also notes Privy's official API/MCP server as an alternate route, though without stating when to prefer it.

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