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

Annotations already cover the safety profile (readOnly, non-destructive, idempotent, closed-world), and the description adds genuine context beyond them: it clarifies the tool performs no action, describes the shape of what it returns, and documents the researched finding that no public EZ Lawn Biller API exists (404 on /api, /developers, /docs; QuickBooks is the only named integration) — which explains why browser automation is the fallback.

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 instruction is front-loaded, but the prose is a run-on with filler ('from ChatGPT, Claude or any AI agent') and an awkward semicolon splice between the return description and the follow-up tool guidance. The API-availability note is relevant but verbose relative to its role.

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 guidance tool with no output schema, the description adequately explains what comes back (step-by-step screens, buttons, fields) and what to do next. It does not describe the format of the returned instructions (text vs. structured) or failure behavior if the feature is absent in the user's plan, which keeps it short of a 5.

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 trivially fully described, so the baseline of 4 applies. There is no argument meaning the description needs to add.

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+resource: it returns step-by-step instructions (screens, buttons, fields) for connecting Stripe inside EZ Lawn Biller, and explicitly notes it 'opens nothing by itself'. That distinguishes it from action-performing siblings, though the opening clause ('Stripe connection in the user's own EZ Lawn Biller account...') largely restates the title and delays the useful part.

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 procedure, then execute it with the cotlet_browser_* tools in the Cloud Browser. What is missing is differentiation from the many ez_lawn_biller_* payment siblings (e.g. automatic_payments, cancel_automatic_payments) — the description never says when this lookup is preferable to those.

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