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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered; the description adds genuinely new facts: it is free, it starts no browser session, and its answer quality degrades gracefully for apps outside the catalog. The only mild tension is "works for any web app" against openWorldHint=false, though this reads as a knowledge-lookup scope rather than a contradiction.

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 lead clause is well front-loaded, but the body is a single long run-on string of comma-separated clauses, and the trailing catalog of six Contractor Foreman actions is bulky. Every element is relevant, yet the content would be far more scannable broken into trigger, scope, and returns sections.

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?

The description tells the agent what it will get back (method, screens, menus, actions, notes, dedicated tools) and when to call it, which is sufficient for a zero-required-parameter lookup tool with full annotation coverage. The main remaining gap is return shape and size (prose vs structured), but no output schema exists to cover it either.

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% and both parameters (app, task) are already documented in the schema, including the Contractor Foreman default. The description adds no format or syntax guidance for either parameter, though the closing action list does hint that the task parameter should name one of those concrete actions.

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 — returns guidance on how to work in an app inside the Cloud Browser — and enumerates what the guidance contains (which browser, sign-in link, step-by-step method, screens/menus/actions, notes, dedicated tools). This is clearly distinguishable from the cotlet_browser_* action siblings, which perform steps rather than describe how to perform them.

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 the description clarifies coverage (any web app; uncatalogued apps get the general method). It does not explicitly say what to do instead when a dedicated tool such as contractor_foreman_create_estimate exists — it only says the guide surfaces those tools — so routing is implied rather than stated.

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