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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=false, and the description is consistent with them, adding that the tool "opens nothing by itself" and returns screens/buttons/fields. The note that no public EZ Lawn Biller API exists (404s on /api, /developers, /docs; only QuickBooks integration) usefully explains why a browser-automation path is required.

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?

Purpose and the critical "returns steps, performs nothing" caveat are front-loaded, and the follow-up action is stated before the API-availability note. The API/404 evidence is slightly verbose but earns its place by justifying the browser-tool handoff.

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 and mostly does: it says what comes back (step-by-step screens, buttons, fields) and what to do next. It could be tighter about what the "link" is and whether the flow differs for the user's own account versus shared access, but nothing essential for correct invocation is missing.

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; baseline 4 applies. The description implicitly confirms no input is needed by describing a pure guidance lookup.

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?

States a specific verb and resource ("Revoke link in the user's own EZ Lawn Biller account") and immediately clarifies that the tool only returns step-by-step instructions rather than performing the action. That distinction is valuable, but the description never defines what kind of "link" is being revoked nor differentiates it from the sibling generate_copy_link beyond the opposite verb.

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?

Explicitly routes usage: call this to get the steps, then perform the action with the cotlet_browser_* tools in the user's Cloud Browser. The context ("from ChatGPT, Claude or any AI agent") is given. It lacks an explicit statement of when NOT to use it (e.g. when the user has no link, or when another revoke/cancel sibling applies).

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