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

The annotations already declare readOnly=true, idempotent=true, openWorld=false, and destructive=false, and the description adds important context beyond them: it 'opens nothing by itself', it returns screen/button/field-level steps, and the official API note explains why browser automation is required. It does not describe the output format in detail or rate limits, but with annotations this is solid disclosure.

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 description is front-loaded with the purpose and the handoff to cotlet_browser_* tools. The API-availability paragraph is longer than necessary, with specific URLs and a date, but it does help explain why no direct integration exists.

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?

With no parameters, no output schema, and rich annotations, the description covers what is needed: what it returns, that it performs no action itself, and what to do next. A small gap remains in not detailing the shape of the returned steps or any limits on the guidance.

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 the schema is empty and the baseline is 4. The description adds meaningful context about what the call returns, though it has no parameters to clarify.

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 uses a specific verb and resource: it 'Returns how to do it in EZ Lawn Biller step by step (screens, buttons, fields)' for Route Optimizer, and it explicitly says it 'opens nothing by itself'. The distinction from action siblings is clear because it is an instruction-returning tool, though it never names the cotlet_browser_* tools or route_map/save_route_changes siblings by full 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?

The description gives clear guidance: use this to learn the steps, then 'do it with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser'. It tells the agent what this tool will not do, but it does not explicitly exclude cases or name specific alternatives beyond the browser tool family.

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