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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new behavioral context: it 'opens nothing by itself' and returns screens/buttons/fields, plus the note that Hipcamp has no public API. This is real value beyond structured fields, though it omits what happens if the user isn't authenticated or whether the guidance is account-specific.

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 front-loaded sentences with the key constraint (opens nothing, use browser tools) placed early. The 'checked 11 Oct 2026' API note is somewhat time-stamped overhead but earns its place by justifying the browser handoff.

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, no-output-schema guide tool, the description covers what it returns (step-by-step screens, buttons, fields) and how to continue the task. It would be complete at 5 with a note on prerequisites such as an active Hipcamp Cloud Browser session.

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?

Zero parameters, so the baseline is 4. There is no input the description needs to explain, and it correctly implies the tool takes no arguments.

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 first sentence names a specific verb and resource (reply to guest) scoped to the user's own Hipcamp account, and the second sentence clarifies the crucial twist that this tool only returns instructions rather than performing the action. The name alone would suggest an action tool, so the description is doing necessary corrective work, but it does so clearly.

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 states the workflow explicitly: call this to get step-by-step guidance, then execute with the cotlet_browser_* tools in the Hipcamp Cloud Browser. It also explains why no direct-API alternative exists, which effectively rules out other approaches. No explicit when-not-to-use or precondition guidance (e.g., login state) is given.

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