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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real context beyond that: it 'opens nothing by itself', it returns procedural steps rather than data, and it names the companion cotlet_browser_* tools needed to actually perform the work. The API-availability note further explains why the browser path is required.

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 is front-loaded well: what it returns, then what it does not do, then how to act on it. The closing paragraph about the official API is over-detailed for the decision at hand, citing URLs that returned 404 and an exact date, which pads the definition without changing how an agent would call it.

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, no-output-schema guidance tool, the description covers what comes back (step-by-step screens, buttons, fields) and what the next action is. The only real gap is scope: it never clarifies which aspects of technician performance the returned walkthrough covers, leaving ambiguity against the adjacent technician_* tools.

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 document; baseline 4 applies. The description correctly implies no inputs are required, keeping expectations aligned with the empty schema.

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 outcome: it 'Returns how to do it in EZ Lawn Biller step by step (screens, buttons, fields)' for technician performance, and explicitly says it 'opens nothing by itself'. That distinguishes it from action tools that mutate data. It does not, however, differentiate it from close siblings such as ez_lawn_biller_technician_pay, _profile, or _credentials, and 'technician performance' itself (dashboards? job counts? revenue?) is never pinned down.

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?

Usage is implied rather than stated: the agent learns to call this first, then 'do it with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser'. That is a useful two-step workflow hint. There is no explicit when-not guidance and no comparison against the other technician_* siblings, so the agent must infer which technician tool answers which question.

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