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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is largely covered upstream. The description does add genuine value by stating it 'opens nothing by itself,' reinforcing that no browser action or side effect occurs. However, it omits details such as how long the returned instructions are, whether they vary by WooCommerce version or plan, or what happens if the user's account differs — modest added context only.

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 scoping statement and the step-by-step return behavior are front-loaded, which is good. But 'from ChatGPT, Claude or any AI agent' and the dangling 'WooCommerce's official API: Yes.' are promotional or unexplained filler that do not help an agent decide or invoke, diluting an otherwise tight statement.

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, no-output-schema helper, the description covers the essentials: what it returns (step-by-step screens/buttons/fields), that it performs no action, and which tool family to use next. The unexplained 'official API: Yes' line leaves a small gap about why that matters, but nothing needed to call it correctly is missing.

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 baseline of 4 applies; there is no parameter behavior left to explain. The description correctly implies a single implicit scope ('the user's own WooCommerce account') rather than suggesting any filter arguments.

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 makes clear this is an instruction-returning tool for getting a WooCommerce sales report, and explicitly clarifies it 'returns how to do it in WooCommerce step by step (screens, buttons, fields) and opens nothing by itself.' The one weakness is the framing 'Get sales report in the user's own WooCommerce account,' which reads like a data-fetch tool before the correction arrives, a mismatch with the actual verb (return guidance, not data).

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 a clear follow-up path: 'then do it with the cotlet_browser_* tools in the user's WooCommerce Cloud Browser,' which tells an agent exactly what to do next. It does not distinguish this from a sibling like cotlet_app_guide or explain when a user should prefer it over the other WooCommerce browser-automation tools, so it stops short of full when/when-not guidance.

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