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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description still earns credit by disclosing the non-obvious trait that it 'opens nothing by itself' and returns instructions rather than results, plus the rationale that Zoopla has no public listings API. It stops short of describing format, length, or freshness of the returned guide.

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?

Purpose is front-loaded in the first clause and the critical 'returns instructions, opens nothing' caveat comes early. The phrase 'from ChatGPT, Claude or any AI agent' is filler, and the closing API-status sentence is long and carries an oddly precise date, but each sentence still contributes relevant context.

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 parameters, no output schema, and rich annotations, the description carries only the burden of explaining what comes back and what to do next — it does both (screens, buttons, fields; then use cotlet_browser_* tools). What is missing is whether the guide is static or account-specific and how an agent should proceed if the user's browser session is not already authenticated.

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 the baseline is 4; there is nothing for the description to disambiguate. The statement that it operates on 'the user's own Zoopla account' implicitly scopes the target, which is the only parameter-like concern here.

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 verb and resource (get listing stats in the user's own Zoopla account) and, importantly, clarifies that it actually returns a step-by-step how-to rather than the data itself. That correction of the name's implication is valuable, but there is no differentiation from plausible siblings such as zoopla_list_my_listings or cotlet_app_guide, so an agent must infer the boundary.

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 a workflow pointer — use this first, then act with cotlet_browser_* tools in the Zoopla Cloud Browser — which is real usage guidance. However, it never says when NOT to use it or which sibling handles adjacent needs (e.g. listing inventory vs. stats), leaving the alternative selection 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.