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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description reinforces this with 'opens nothing by itself', which is the key behavioral fact for an agent that might otherwise expect a browser session to launch. It also discloses the return shape at a high level ('screens, buttons, fields'). It does not cover whether the guidance is cached/static or freshness-sensitive, but that is a minor omission for a zero-parameter read-only tool.

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 facts (returns step-by-step guidance, opens nothing itself, follow with cotlet_browser_* tools) are front-loaded and useful, but the closing line about Immobiliare.it having no public API is tangential to selecting this tool and repeats the product name twice in one sentence. The embedded 'checked 11 Oct 2026' date is noise for an agent deciding whether to call it.

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 zero-parameter, read-only guidance tool with no output schema, the agent needs to know what comes back and what to do next, and the description covers both ('step by step (screens, buttons, fields)' and the cotlet_browser_* handoff). The API-availability note preempts an agent's attempt to look for an official endpoint. It stops short of describing how the steps terminate or what a successful end state looks like.

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 no parameters, which is the baseline-4 case; there is no schema surface the description needs to compensate for. The description is consistent with an argument-free tool and adds nothing misleading about inputs.

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 the resource (the user's own Immobiliare.it listings) and clarifies the non-obvious fact that the tool returns step-by-step instructions rather than listing data. It signals the handoff to cotlet_browser_* tools, which separates it from the browser siblings. The only drag is that the leading phrase 'List my listings' reads like a data-retrieval verb while the tool actually returns guidance, so the agent must read to the second sentence to disambiguate.

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 clear sequencing guidance: this tool 'opens nothing by itself', and the actual work is then done 'with the cotlet_browser_* tools in the user's Immobiliare.it Cloud Browser'. That tells the agent it is a first step in a chain rather than a standalone action. It does not state when NOT to use it (e.g. versus immobiliare_create_listing or reply_to_message), so exclusions are left implicit.

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