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

Annotations already declare readOnly/idempotent/non-destructive, and the description is consistent with them while adding real context: the call performs no browser action, and follow-up automation must go through cotlet_browser_* tools. The note that no public EZ Lawn Biller API exists (404s on /api, /developers, /docs; QuickBooks the only named integration) explains why the browser route is required — useful behavioral context beyond the annotations.

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 operative guidance is front-loaded in the first two sentences, which is good. The third sentence is a long verbatim research citation (dated URL-by-URL audit) that is only tangentially needed to call the tool, and the phrase 'in the user's own EZ Lawn Biller account' recurs, adding some redundancy.

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 covers what it returns (step-by-step screens, buttons, fields), what it does not do (open anything), and what to use next. The only shortfall is that the scope of 'delivery tracking' in EZ Lawn Biller is never spelled out, so an agent cannot fully predict whether the returned steps match the user's intent.

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?

There are zero parameters, so there is no parameter semantics to convey; the baseline for a no-param tool applies. The description correctly implies no inputs are needed.

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/instruction tool that 'Returns how to do it in EZ Lawn Biller step by step (screens, buttons, fields)' rather than a data-reading or mutating operation, which is a meaningful distinction among the many action-oriented siblings. The specific verb+resource is present, though 'delivery tracking' itself is never defined (routes vs. customer deliveries), leaving some ambiguity against ez_lawn_biller_customer_delivery_settings.

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 an explicit workflow: call this to get the steps, then 'do it with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser.' It also explicitly states the tool 'opens nothing by itself,' clarifying what this call does not accomplish. It stops short of naming a when-not condition or a sibling alternative, but the sequencing guidance is clear.

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