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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true, and the description reinforces this by stating it 'opens nothing by itself' — resolving the apparent conflict with the 'delete' name. It also explains the absence of a public EZ Lawn Biller API, which justifies the browser-automation follow-up. It does not describe output format or failure behavior, keeping it below 5.

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 purpose and the follow-up routing are front-loaded and useful, but the closing sentence about 404s on ezlawnbiller.com/api, /developers and /docs plus the QuickBooks FAQ detail is verbose justification that does not help an agent select or invoke the tool. That paragraph could be compressed to a single clause.

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 zero parameters, no output schema and annotations already covering the safety profile, the description supplies what an agent needs: what it returns and how to carry out the action afterwards. A note on what the returned instructions look like or how to handle an unrecognized service would make it fully complete.

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, so the baseline is 4 and there is no parameter semantics to add. The description correctly implies a zero-argument, account-scoped informational call with no input to specify.

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 makes the actual behavior specific: it returns step-by-step instructions (screens, buttons, fields) for deleting a one-time service rather than performing the deletion. That distinguishes it from the cotlet_browser_* tools it points to. It does not explicitly distinguish it from nearby siblings like ez_lawn_biller_edit_one_time_service or ez_lawn_biller_delete_service_type, so it stops short of a 5.

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 explicitly routes the agent: use this to get the procedure, then execute with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser. What is missing is a when-not-to-use statement or a named alternative among the other delete/edit siblings, so the guidance is clear but not exhaustive.

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