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

Annotations already establish read-only, idempotent, non-destructive, non-open-world behavior, and the description adds genuinely useful context beyond that: it is free and consumes no browser session, and it degrades gracefully to a general method for uncatalogued apps. It does not describe the shape or length of the returned guidance, so an agent cannot anticipate output volume.

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 purpose is front-loaded, but the first sentence is a rambling enumeration of what the guide covers, and the closing fragments ("Free, no browser session.") read as clipped notes rather than integrated prose. Trimming the itemized list would improve it without losing information.

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 two-parameter, no-output-schema guidance tool with full annotation coverage, the description supplies the key facts an agent needs: what it returns conceptually, when to call it, its cost, and its fallback behavior for uncatalogued apps. Only the re-use/re-call policy is genuinely 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?

Schema description coverage is 100%, with both `app` (including its Cronometer default) and `task` documented in the schema itself. The description adds no meaning about how `task` shapes the returned guidance or how an unknown `app` name is resolved, so it does not exceed the schema baseline.

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 resource and output: guidance on working in an app, including which browser and sign-in link to use, the step-by-step method, screens/menus/actions, notes, and any app-specific tools. That distinguishes it from the browser_* action siblings, though the long comma-separated enumeration makes the core purpose slower to grasp than a single crisp sentence would.

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?

"Call it before the first browser step in an app" is an explicit trigger condition, and the note about apps outside Cotlet's catalog still getting the general method sets expectations for coverage. It does not say whether to re-call for a second task in the same app, which leaves a minor gap.

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