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

The description adds real context beyond the annotations: it explicitly says the tool "opens nothing by itself," which corroborates readOnlyHint=true and destructiveHint=false and reassures the agent that no browser session is spawned. It also discloses a useful external constraint (no public API, webhooks or Zapier; only QuickBooks and Stripe integrations), which steers the agent away from an API-based approach. The gap is that it never says what the returned payload looks like (plain text steps, a link, a session handle).

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 is stated up front and the workflow follows logically, but the second sentence is overloaded, packing the no-side-effects note, the sibling-tool handoff, and an API availability audit into one clause. The "checked 9 Nov 2026" provenance adds bulk without helping the agent decide or act.

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, no output schema, and read-only annotations, the description covers the essential safety and workflow picture. However, for a tool whose entire value is a returned guide, the absence of any statement about the response shape or length leaves a genuine hole. The missing comparison against cotlet_app_guide also matters given how many sibling tools exist.

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 baseline for a no-arg tool applies. The description does not introduce phantom parameters or suggest any input is needed, which is consistent with the empty schema.

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 does say concretely what comes back ("how to do it in LawnBoss step by step (screens, buttons, fields)"), but it frames the tool as "List customers" when the tool actually returns a procedure rather than customer data. That tension between name/title and delivered output leaves the agent guessing whether it gets a list or a guide. It is neither tautological nor clearly differentiated from the sibling cotlet_app_guide, which sounds like it serves a similar guiding role.

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?

There is an implied workflow: call this to get the steps, then execute them with cotlet_browser_* tools in the user's LawnBoss Cloud Browser. What is missing is when to prefer this over cotlet_app_guide, or over the action siblings like lawnboss_create_estimate, and whether this must always precede those actions. Usage is inferable but not stated as a rule.

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