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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, and the description reinforces this by stating it performs no action itself and only returns procedural guidance — a genuinely useful clarification of what an agent gets back. The added note about no self-serve API key explains why browser tools are required, though the sentence is awkwardly worded and partly tangential.

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 payload — returns step-by-step instructions, then act via cotlet_browser_* — is front-loaded and useful, but the final sentence about the ProSolutions Paired host and API keys is dense, hard to parse, and only loosely connected to the tool's behavior.

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, no output schema and full annotation coverage, the description carries the right load: it explains what comes back (screens, buttons, fields) and what to do next. Only the ambiguity versus the similar configure_promotion sibling keeps it short of complete.

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 the schema imposes no semantic burden and there is nothing for the description to compensate for. Baseline of 4 applies.

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?

States a specific verb and resource ('Configure online promotion') plus the account scope ('user's own Paired Plus account'). It is clear what the tool is for, though it never distinguishes itself from the near-identical sibling paired_plus_configure_promotion, so an agent must guess between them.

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?

Gives concrete operational context: the tool returns step-by-step instructions and 'opens nothing by itself', so the agent must follow up with cotlet_browser_* tools. That is real when-and-how guidance, but there is no explicit statement of when to pick this over the other configure_* siblings or any exclusions.

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