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

Goes beyond the annotations by confirming no side effect occurs ('opens nothing by itself') and by explaining WHY browser automation is required — LawnBoss publishes no public API, webhooks or Zapier app, and connects only to QuickBooks and Stripe. The dated verification note is a useful provenance signal. It does not describe the return payload's shape, which keeps it short of a 5.

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?

Front-loads the action and the key caveat in the first sentence, then the handoff, then the supporting rationale. Three sentences with no filler, though the parenthetical date and provider list cost some space for modest payoff.

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 guide tool with no output schema, the description covers what it returns (screens, buttons, fields), what it does not do, and which tool family to use next. The only gap is the precondition of an already-open LawnBoss Cloud Browser session, which the agent must infer.

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 for a parameterless tool applies, and the description correctly stays silent on inputs rather than inventing them.

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 ('Schedule job in the user's own LawnBoss account') and immediately disambiguates what the tool actually does: it returns step-by-step instructions rather than performing the scheduling. That distinction separates it from the mutating siblings and from the cotlet_browser_* primitives.

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?

Gives a clear next step ('then do it with the cotlet_browser_* tools in the user's LawnBoss Cloud Browser') and an explicit exclusion ('opens nothing by itself'). It does not explicitly contrast with lawnboss_reschedule_job, but the schedule/reschedule split is self-evident from the names.

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