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

Annotations already declare readOnlyHint=true, openWorldHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the call performs no navigation or mutation and only returns procedural instructions, and it notes there is no public Immobiliare.it API, explaining why browser automation is required. The dated 'checked 11 Oct 2026' API caveat is somewhat tangential to this tool's behavior.

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 key clarification (returns instructions, does not act) is front-loaded, but the final sentence about the missing official API is long, redundant with the first clause, and includes a parenthetical date that adds little for tool selection. The sentence structure is a run-on chain of clauses rather than cleanly separated points.

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 zero parameters, no output schema and a simple read-only nature, the definition covers what an agent needs: what comes back (step-by-step instructions), that nothing is opened, and which tools to use next. It could be slightly stronger by indicating the rough shape or granularity of the returned steps, but nothing essential is missing.

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 input schema is an empty object with no parameters, so there is no parameter semantics to document; the baseline for a zero-parameter tool applies. The description does not invent or misdescribe any 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 states a specific outcome: it returns a step-by-step guide (screens, buttons, fields) for saving a search in the user's own Immobiliare.it account, rather than performing the save. It explicitly distinguishes itself from the sibling browser tools by saying it 'opens nothing by itself' and that the actual work is done with cotlet_browser_*. The opening sentence 'Save search in the user's own account' slightly oversells the action before the correction, which keeps it from a 5.

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 names the follow-up path clearly: use the cotlet_browser_* tools in the user's Immobiliare.it Cloud Browser to execute the steps. It does not spell out a negative case (e.g., when a user already has a saved search or when to prefer a different sibling), but the read-then-act workflow is unambiguous.

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