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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the bar is lower. The description still adds real value beyond them: it says the tool opens nothing by itself, describes the return shape as step-by-step screen/button/field guidance, and explains that no official EZ Lawn Biller API exists (endpoints 404, QuickBooks is the only named integration), which is exactly the context an agent needs to understand why browser automation is the execution path.

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 facts are front-loaded: what it returns, that it has no side effects, and what to do next. The final sentence about 404s on /api, /developers and /docs is somewhat verbose, but it substantiates the claim that browser automation is required rather than being pure filler.

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 tool with no output schema, the description covers the mechanism and the return format well. The gap is scope: 'future-week changes' is never defined in terms of what kinds of changes (visits, routes, pricing, schedules) are covered, so an agent cannot judge whether this guidance applies to its specific request.

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 an empty object with additionalProperties=false, so there is nothing for the description to disambiguate. Baseline 4 applies for a parameterless 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 making future-week changes in the user's own EZ Lawn Biller account. It also makes clear this is a guidance/knowledge tool rather than an executor ('opens nothing by itself'). It does not, however, distinguish itself from action-performing siblings such as ez_lawn_biller_copy_to_future_weeks or ez_lawn_biller_apply_to_all_weeks.

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?

There is an explicit follow-on instruction: retrieve the steps here, then execute them with the cotlet_browser_* tools in the EZ Lawn Biller Cloud Browser. What is missing is any routing guidance against alternatives — an agent cannot tell from this text why it should call this instead of a sibling that actually performs future-week changes.

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