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

Annotations already declare readOnly, idempotent, non-destructive and non-open-world, so the safety profile is covered. The description adds genuinely non-redundant behavior: the tool performs nothing itself, returns screen/button/field-level steps, and — via the API note — explains why no direct integration path exists. The dated 404/FAQ evidence is unusual but does disclose a real constraint on how the data can be reached.

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 clear, but the API sentence is bloated with a specific date, three probed URLs, and an FAQ citation that a calling agent does not need. The opening clause "from ChatGPT, Claude or any AI agent" adds no decision-relevant information.

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 definition covers what an agent needs: what it returns (step-by-step screens/buttons/fields), what it does not do (opens nothing), and which tool family to use to act on the guidance. Only the scope of "phone numbers" (view vs. create vs. edit) is left unstated.

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 and the schema is empty with additionalProperties false, so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter-level confusion is possible.

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 a guidance/knowledge tool: it "returns how to do it in EZ Lawn Biller step by step (screens, buttons, fields) and opens nothing by itself." That distinguishes it from an action tool, which is the key ambiguity here. The residual weakness is that "Phone numbers" is a bare noun phrase — it never states whether the guidance covers viewing, adding, or editing phone numbers.

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 explicitly routes the agent: read this for the procedure, "then do it with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser." That is a concrete when-to-use/where-to-go-next instruction rather than an implied one. It stops short of contrasting itself with the numerous ez_lawn_biller_* sibling tools, so an agent still has to infer that those are separate from this guide.

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