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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: it performs no action itself, it returns a screen-by-screen procedure (screens, buttons, fields), and it must be paired with cotlet_browser_* tools. That is real value beyond the annotations.

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?

Three sentences, front-loaded with what the tool does and what it returns, followed by the required follow-up tooling. Minor waste in 'from ChatGPT, Claude or any AI agent' and in the self-referential 'Hipcamp's official API: Hipcamp has no public API' phrasing.

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 full annotation coverage, the description supplies everything an agent needs: it explains that the response is an instructional procedure rather than data and that execution happens through browser tools. Only sibling routing guidance is absent.

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 and there is no parameter meaning the description could add. Nothing is missing or misdescribed on this dimension.

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 bookings in the user's own Hipcamp account) and clarifies the actual behavior: it returns step-by-step instructions rather than booking data, and 'opens nothing by itself'. That disclosure resolves the name/behavior ambiguity, though it never distinguishes this tool from sibling Hipcamp actions such as hipcamp_reply_to_guest or hipcamp_update_pricing.

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 implies the workflow clearly enough: call this first for the procedure, then execute with cotlet_browser_* tools in the user's Hipcamp Cloud Browser. It also notes Hipcamp has no public API, which forecloses an API-based alternative. However, there is no explicit when-not-to-use statement and no routing versus the other hipcamp_* tools.

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