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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorldHint=false. The description adds genuinely useful context beyond that — 'Free, no browser session' tells the agent there is no cost or live browser state to manage. However, it says nothing about the shape or size of the returned guidance, which matters for a tool whose whole output is prose.

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 instruction ('Call it before the first browser step in an app') is buried mid-paragraph after a long comma-separated inventory of what the guide contains. The nine-item CharlieHR action list consumes roughly a third of the text and is informative but bulky; the whole thing reads as one run-on sentence rather than front-loaded guidance.

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?

With no output schema, the description correctly compensates by enumerating what the guide returns: browser choice, sign-in link, method, screens, menus, actions, notes, and dedicated tools. Combined with the explicit 'call before first browser step' trigger and the free/no-session note, an agent has enough to invoke it correctly; only the return format is left vague.

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 coverage is 100%, so both parameters are already documented, including the 'Default: CharlieHR' behavior and max lengths. The description only adds that the guide is app-scoped and enumerates CharlieHR's covered actions, which hints at the level of detail returned rather than clarifying parameter usage. 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 makes clear this is a guidance/knowledge tool that returns instructions for operating a given app in the Cloud Browser: browser choice, sign-in link, step-by-step method, screens/menus/actions, notes, and dedicated tools. It distinguishes itself from the browser_* siblings by being the pre-step orientation rather than an action, though the opening phrase 'How to work in an app' restates the title rather than leading with a verb like 'Returns instructions for...'.

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 an explicit trigger: 'Call it before the first browser step in an app,' plus scope ('Works for any web app; one outside Cotlet's catalog gets the general method'). It also signals that app-specific dedicated tools may exist. It stops short of telling the agent when to skip this guide, e.g. whether to prefer charliehr_* tools directly once known.

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