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

Annotations already cover read-only, idempotent, non-destructive, closed-world nature, and the description adds meaningful behavior: it returns instructions only and performs no action. It also discloses the external constraint that Hostelworld has no public API for property owners, a genuinely useful fact. It does not mention auth/session requirements beyond 'the user's own account'.

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?

Front-loads the purpose and the no-side-effect constraint well, but the phrase 'from ChatGPT, Claude or any AI agent' is marketing filler that does not help an agent decide or invoke. The API note is useful but reads as appended trivia.

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 carries the burden of describing the return value and does so (screens, buttons, fields, step by step). It also points to the follow-up tooling, leaving little ambiguity for a zero-parameter tool.

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; the description correctly implies no input is needed. Nothing further is required of it.

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?

Names a specific resource (Hostelworld payouts report) and, crucially, clarifies the deliverable: step-by-step instructions rather than the report data itself. That distinguishes it from the cotlet_browser_* siblings that actually perform the actions, though the verb 'Get' alone would not.

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?

Explicitly states it 'opens nothing by itself' and that the agent must then act using the cotlet_browser_* tools in the Cloud Browser, which is clear chaining guidance. No explicit when-not-to-use case is given, keeping it short of a 5.

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