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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuine context beyond them: "Free, no browser session" tells the agent the call costs nothing and does not open a Cloud Browser session, and the catalog-vs-general-method behavior is disclosed. It says nothing about the shape or size of the returned guidance.

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 content is front-loaded with the purpose and trigger, but the opening sentence is a dense, comma-chained list of guide contents that is harder to parse than it needs to be. It is not padded, but the list could be tightened.

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 read-only, zero-required-parameter informational tool with no output schema, the description covers what it returns, when to call it, and its fallback behavior. The remaining gap is any hint about the volume or structure of the returned guide, which matters for an agent planning context budget.

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' (name or Cotlet slug, default EstimateOne) and 'task' (user's goal in their words) documented in the schema. The description only echoes that the guide is tailored per app and per workspace; it adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 a concrete verb+resource: it returns guidance on working in a specific web app through Cotlet's Cloud Browser tools, and it enumerates what the guide contains (browser choice, sign-in link, method, screens/menus/actions, notes, dedicated tools). It implicitly differentiates itself from the browser_* siblings by being the preparation step, though it never names a specific sibling tool.

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" gives an explicit trigger point and ordering relative to the browser tools. It also clarifies fallback behavior (apps outside the catalog get the general method), but gives no explicit when-not-to-call condition.

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