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

The description adds substantial behavior beyond the readOnly annotations: it explicitly says the tool opens nothing by itself and returns instructions with screens, buttons, and fields. It also explains why browser tools are needed by noting Hipcamp has no public API, which helps the agent understand the operating model.

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 description is reasonably front-loaded and every sentence contributes useful context. Some phrasing, such as 'from ChatGPT, Claude or any AI agent', is slightly promotional and could be trimmed without losing meaning.

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 guide tool with no output schema, the description is nearly complete: it says what the tool returns and how to act on it. It could mention any prerequisite such as the user already being logged into Hipcamp, but that is a minor gap.

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?

There are zero parameters, so the baseline is 4. No additional parameter semantics are needed or expected.

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 makes clear that this tool returns step-by-step Hipcamp calendar sync instructions rather than performing the sync itself. It distinguishes itself from the cotlet_browser_* execution tools by explicitly saying it opens nothing and the browser tools should be used afterward. The opening phrase 'Sync calendar' is somewhat misleading, but the second sentence corrects it.

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 a clear workflow: call this tool to retrieve Hipcamp UI steps, then execute them with cotlet_browser_* in the user's Hipcamp Cloud Browser. It implies that direct execution should use browser tools instead, but it does not explicitly state when not to use this guide tool or name any other non-browser alternative.

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