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 meaningful context beyond that: it explicitly says the tool 'opens nothing by itself' and that the return payload is procedural guidance (screens, buttons, fields), which tells the agent this is a knowledge/instruction tool, not an actor.

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 front-loaded sentence carries the useful information, but the opening clause ('from ChatGPT, Claude or any AI agent') largely restates the title, and the trailing paragraph about 404s on ezlawnbiller.com/api, /developers and /docs is research backstory that does not help an agent decide or invoke. Roughly a third of the text is not load-bearing for tool selection.

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-destructive guidance tool with no output schema, the description covers everything needed: what it returns, that it has no side effects, and which tools to use afterward. The API-availability note, while verbose, preempts an agent from hunting for a direct integration path.

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 no parameter semantics to explain and the baseline of 4 applies. The description correctly implies no inputs are required before calling it.

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 states a specific resource (customer search in EZ Lawn Biller) and, crucially, clarifies that the tool returns step-by-step instructions (screens, buttons, fields) rather than performing the search. That verb distinction keeps it from being confused with a data-returning tool, though it never names a sibling such as customer_list or customer_dashboard to sharpen the boundary.

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 workflow: read the steps here, then execute them with the cotlet_browser_* tools in the user's Cloud Browser. There is no explicit when-not-to-use guidance and no named alternative for an agent that just wants customer data directly, so the usage context is implied rather than fully delineated.

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