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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false. The description adds genuine context beyond them: it states the tool performs no action ('opens nothing by itself'), that the return value is step-by-step screen/button/field instructions, and that the actual execution must happen through browser tools. The API-availability note explains why a guide rather than a direct API call exists.

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 operative sentences are front-loaded and efficient, but the closing API note is bloated with research minutiae (specific paths, 404 results, the date 11 Nov 2026) that could be compressed to one clause. That detail is tangential to calling the tool correctly.

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 input parameters and no output schema, the description carries the burden of explaining the return value, and it does: step-by-step screens, buttons and fields, plus the required follow-up with browser tools. It is nearly complete; a note on prerequisites (e.g., user must be signed into EZ Lawn Biller) would close the last gap.

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; the empty schema with additionalProperties=false is self-explanatory. Baseline of 4 applies for a correctly 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 makes clear this is a procedural-guidance tool, not an executor: it 'Returns how to do it in EZ Lawn Biller step by step (screens, buttons, fields) and opens nothing by itself.' That resolves the ambiguity created by the action-oriented name 'bill_now.' It does not differentiate itself from close siblings such as ez_lawn_biller_bill_the_customer or ez_lawn_biller_bill_held_periods, so an agent cannot tell from the text which of these to pick.

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?

Usage context is explicit: call this to get the steps, then perform them with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser. That names the follow-on alternative tool family and the handoff condition. It gives no exclusion guidance relative to the other bill_* siblings, which is the main gap.

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