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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds meaningful context beyond that: the tool performs no action in the account itself and only returns procedural guidance, so an agent knows it must complete the task through separate browser tools. The note that no public EZ Lawn Biller API exists further explains why the browser-automation route 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 behavior and the follow-up instruction are front-loaded in the first two sentences, which is good structure. The final sentence, however, spends substantial length on API-discovery forensics ('returned 404', FAQ and manual naming QuickBooks) that an agent does not need in order to select or call the tool — it could be compressed to 'no public API; use browser tools.'

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, no-output-schema tool, the definition covers what is returned, why it returns guidance rather than acting, and how to act on it next. The one genuine gap is routing among the several similarly named schedule-PDF siblings, which the description does not address.

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 disambiguate and the baseline is 4. The schema is an empty object with additionalProperties false, consistent with the description's framing as a parameterless guidance lookup.

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 names a specific resource (schedule PDF in EZ Lawn Biller) and states precisely what the tool returns: step-by-step instructions covering screens, buttons and fields. It also explicitly negates the verb in the name ('opens nothing by itself'), which resolves the misleading 'open' title. What it does not do is differentiate from near-namesake siblings such as ez_lawn_biller_open_pdf or ez_lawn_biller_download_schedule_pdf.

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 follow-up path: read the steps here, then execute them with the cotlet_browser_* tools in the user's Cloud Browser. That is real when-to-use context. However, it never says when to choose this over the many other schedule/PDF siblings, nor what would make this unnecessary — the alternative selection is left to inference.

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