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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, and the description is consistent with them ('opens nothing by itself'). It adds genuinely useful context beyond annotations: the return is a step-by-step how-to, and LawnBoss has no public API, webhooks or Zapier app, which steers the agent away from trying an API path. It does not describe failure modes (e.g., job not found) or any account/auth prerequisite.

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 required next step are front-loaded in the first two clauses, so an agent gets the essentials immediately. The trailing API note is a somewhat awkward fragment ('LawnBoss's official API: ...'), but it still carries actionable information rather than filler.

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 is returned (screens, buttons, fields) and what to do next, which is the essential context. Missing are edge cases such as what happens when the target job does not exist or is not accessible.

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 applies. No parameter-related meaning is missing.

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 the resource (a job in the user's LawnBoss account) and clarifies the actual behavior: it 'Returns how to do it in LawnBoss step by step (screens, buttons, fields) and opens nothing by itself.' That resolves the tension with the action-sounding name. It does not distinguish itself from cotlet_app_guide, which appears to serve a similar guide function.

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 clear workflow context: call this first to get the steps, 'then do it with the cotlet_browser_* tools in the user's LawnBoss Cloud Browser.' That tells the agent both the use case and the required follow-up. It offers no explicit exclusions or comparison against lawnboss_schedule_job for the new-vs-existing-job case.

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