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

Annotations already declare readOnlyHint=true and destructiveHint=false, which would otherwise read as contradictory for a "remove" tool; the description earns credit by explaining why — it returns guidance and opens nothing. It also discloses that no public EZ Lawn Biller API exists (404s at /api, /developers, /docs), justifying the browser-tool handoff. It stops short of covering authentication state or what happens if the user is not signed in.

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 browser-tool handoff are front-loaded, which is good. However, the closing sentence enumerating specific 404 URLs and the FAQ's mention of QuickBooks is verbose relative to its usefulness and reads like research notes appended to the definition.

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 parameters and no output schema, the description carries the burden of explaining what comes back, and it does (step-by-step screens, buttons, fields). The account scoping and the execution path via cotlet_browser_* are both stated. Minor gaps remain around preconditions such as an authenticated browser session.

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 no parameter meaning to convey and the baseline of 4 applies. The description correctly implies a no-argument invocation scoped implicitly to the caller's own account.

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 verb and resource ("Remove saved card in the user's own EZ Lawn Biller account") and then immediately clarifies the tool's actual nature: it returns step-by-step instructions rather than performing the removal. This resolves the potential confusion created by a name that sounds like a mutation. It does not explicitly contrast itself with the sibling ez_lawn_biller_change_saved_card, which is why it falls 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?

"Then do it with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser" gives concrete follow-up guidance on how the removal is actually executed. "Opens nothing by itself" sets a clear expectation about what this call will and will not accomplish. There is no explicit statement of when-not-to-use or a named alternative among the ez_lawn_biller_* siblings.

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