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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and the description reinforces this by stating it 'opens nothing by itself' and only returns instructions. It also discloses that Hostelworld has no public API for property owners, which usefully prevents an agent from attempting an API path. It does not describe the shape or length of the returned steps, which would be the remaining behavioral detail.

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 essential facts (what it returns, that it performs no action, and which tools finish the job) are front-loaded across three tight sentences. The phrase 'from ChatGPT, Claude or any AI agent' adds no operational value and could be cut without loss.

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 rich annotations, the description supplies everything an agent needs: it is a guidance-only tool, it returns procedural steps, and the browser tools carry out the work. The only gap is that the returned step content is not characterized beyond 'screens, buttons, fields'.

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 there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. No parameter information is needed or missing.

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 a specific verb and resource (list reservations) and immediately clarifies what the tool actually returns: step-by-step Hostelworld screens, buttons and fields, not the reservation data itself. It distinguishes itself from the cotlet_browser_* siblings by stating it 'opens nothing by itself'. The opening clause ('List reservations in the user's own Hostelworld account') is slightly misleading until the second sentence corrects it, which keeps this 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 gives clear sequencing guidance: call this to get the steps, then execute them with the cotlet_browser_* tools in the Hostelworld Cloud Browser. It does not state any when-not-to-use conditions or mention non-browser alternatives, but the workflow context is explicit enough that an agent knows where this tool sits.

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