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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-redundant behavior: the tool 'opens nothing by itself' and returns procedural guidance rather than data, which tells the agent it must chain into the browser tools to accomplish anything.

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 instruction is front-loaded and the step-by-step return is stated early, which is good. However, 'from ChatGPT, Claude or any AI agent' is filler, and the closing API note is phrased redundantly ('ChowNow's official API: ChowNow has no API...') with a dated verification stamp that adds bulk without helping invocation.

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 output schema and no parameters, the description has to carry the return-value burden, and it does — it names the granularity of the guidance (screens, buttons, fields) and the required browser tools. What is missing is only the concrete shape of that returned guidance, which is a minor gap for a zero-argument read-only tool.

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 beyond what the empty schema already shows. Baseline for a no-parameter tool 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?

The first clause states a specific verb and resource ('List orders in the user's own ChowNow account'), but the second sentence reveals that the tool does not actually return orders — it 'Returns how to do it in ChowNow step by step (screens, buttons, fields)'. That mismatch between the nominal purpose and the real behavior is disambiguated, but only after the agent has read past the headline claim.

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 clearly specifies the downstream workflow: use the cotlet_browser_* tools in the user's ChowNow Cloud Browser, and it pre-empts the obvious alternative by noting ChowNow has no owner-accessible API. It does not distinguish itself from adjacent ChowNow siblings (e.g. chownow_list_customers) or from cotlet_app_guide, so routing among the guide-style tools is left to inference.

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