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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false, so the agent knows the safety profile. The description adds genuinely non-obvious behavioral context beyond that: it 'opens nothing by itself' and returns procedural content rather than data, which is exactly the trait an agent would otherwise misjudge from the 'list orders' name. It stops short of describing the shape or 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 core clarification — that it returns a walkthrough and opens nothing — is front-loaded and valuable. But 'from ChatGPT, Claude or any AI agent' is promotional filler, and the trailing fragment 'WooCommerce's official API: Yes.' is cryptic and adds no actionable meaning for an agent.

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, read-only guidance tool with no output schema, the description supplies the two things an agent needs: what it returns (procedural steps) and what to do next (cotlet_browser_* tools). The absence of any hint about the returned guide's structure is a minor gap given the tool's simplicity.

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 schema declares zero parameters with additionalProperties false, so there is nothing for the description to disambiguate. Baseline for a no-parameter tool applies, and the description does not mislead about inputs.

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 the unusual nature of the tool explicit: it returns step-by-step instructions (screens, buttons, fields) for listing orders rather than the orders themselves, and names the cotlet_browser_* tools that perform the action. This is a specific verb+resource pairing that an agent can distinguish from sibling mutation tools like woocommerce_update_order_status. The only weakness is the initial framing 'List orders in the user's own WooCommerce account', which briefly suggests a data-returning tool before the second sentence corrects it.

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?

The description gives a clear next-step ('then do it with the cotlet_browser_* tools in the user's WooCommerce Cloud Browser'), which effectively tells the agent this is a prerequisite/planning call. However, it offers no guidance on when to call this versus sibling tools such as woocommerce_get_sales_report or woocommerce_update_order_status, and no exclusions or preconditions.

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