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, and the description stays consistent with them by stating it 'opens nothing by itself.' It adds genuinely useful context beyond the annotations: the lack of a public EZ Lawn Biller API (404s on /api, /developers, /docs; QuickBooks named as the only integration), which explains why UI automation is needed.

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 key constraint ('opens nothing by itself') and the handoff to cotlet_browser_* tools are reasonably front-loaded in the second sentence. However, the single run-on sentence with colon-and-semicolon chaining, plus the appended API-history sentence, makes it denser and harder to scan than it needs to be for a zero-parameter tool.

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 no-parameter, read-only guidance tool with no output schema, the description covers what is returned (step-by-step screens, buttons, fields), that no side effect occurs, and which tool family to use afterward. The only modest gap is that it does not indicate how the step-by-step content is scoped or presented when the user's account differs from the default UI.

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 no parameters and the schema is fully closed (additionalProperties false, 100% coverage), so there is nothing for the description to disambiguate. Baseline 4 applies for a zero-parameter tool.

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 verb-and-resource: it returns step-by-step instructions (screens, buttons, fields) for the 'Day assignment drawer' in EZ Lawn Biller, and explicitly says it opens nothing itself. That distinguishes it from action-performing tooling, though it does not differentiate it from the many other ez_lawn_biller_* guidance siblings beyond the subject-matter label in the name.

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 use path: call this to learn how, then perform the action with the cotlet_browser_* tools in the user's Cloud Browser. It does not spell out when NOT to use it or how it relates to adjacent ez_lawn_biller_* tools, so the routing guidance is clear but not exclusionary.

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