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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered; the description still adds real value by stating the tool only returns instructions and 'opens nothing by itself,' which pre-empts a caller assuming it mutates the account. The note that Service Autopilot has no public API or self-service keys explains why browser automation is the execution path. It does not describe the shape of the returned step-by-step content beyond parenthetical field types.

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?

Three sentences, each carrying a distinct payload: what it returns, that it acts on nothing, and what to use next, with the API absence as justification. The lead clause 'from ChatGPT, Claude or any AI agent' is filler and the API sentence is somewhat tangential, but nothing is genuinely misleading or bloated.

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, non-mutating guide tool with no output schema, the definition covers what is returned, that nothing is executed, and which tools to chain into for execution. The only gap is a description of the returned guidance format (plain text? structured steps?), which matters somewhat for agent parsing.

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 nothing for the description to disambiguate and the baseline is 4. No parameter claims are made that could conflict with the empty 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 description gives a specific verb and resource — it returns step-by-step instructions (screens, buttons, fields) for adding a client in Service Autopilot — and explicitly counters the mutating implication of the name by saying it 'opens nothing by itself.' It also distinguishes itself from the cotlet_browser_* siblings that actually perform the action. The opening clause restating the name plus the 'ChatGPT, Claude or any AI agent' phrasing adds a little noise, keeping it short of a 5.

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 workflow guidance: use this to get the procedure, then execute with cotlet_browser_* tools in the user's Service Autopilot Cloud Browser. That names the alternative and the sequence. It stops short of stating when NOT to use it (e.g., versus the sibling cotlet_app_guide, which is never differentiated).

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