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

The description goes well beyond the annotations by stating there are no side effects ('opens nothing by itself'), naming the execution path required (Cloud Browser plus cotlet_browser_* tools), scoping it to the user's own account, and explaining why automation is needed at all (no public API, 404s on /api, /developers, /docs). That resolves the apparent tension between the 'delete' name and readOnlyHint=true rather than contradicting it.

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 workflow are front-loaded and useful, but the closing API-investigation sentence is long, semicolon-chained, and partly irrelevant to invoking the tool (specific probe date, 404 URLs, QuickBooks mention). Trimming that would sharpen the definition without losing anything an agent needs.

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 guidance tool with no output schema, the description tells the agent what comes back (step-by-step screens, buttons, fields) and what to do next. It stops short of describing the response shape or whether the steps are visit-specific, which would matter for a 'delete visits' instruction set.

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 baseline is 4 and there is nothing for the description to add. It does not introduce any parameter-like concepts that would confuse the caller.

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 concrete verb and resource (delete visits in the user's EZ Lawn Biller account) and, crucially, clarifies that the tool returns step-by-step instructions rather than performing the deletion. That disambiguates it from the sibling delete_* tools, though it never explicitly names a sibling or says which visit types it covers versus ez_lawn_biller_delete_draft or delete_one_time_service.

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 two-step workflow: call this to get the screens/buttons/fields, then execute with the cotlet_browser_* tools in the user's Cloud Browser. What's missing is any exclusion or routing rule among the many sibling delete tools, so an agent still has to guess when this visit-deletion guidance applies versus the other delete variants.

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