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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description reinforces this with 'opens nothing by itself', which prevents an agent from assuming the pricing was changed. It goes further by disclosing the return format (step-by-step screens/buttons/fields) and the external constraint (Hipcamp has no public API, checked on a stated date) — context no annotation or schema field carries.

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 with the most decision-relevant fact (it returns instructions, does not act) placed early, followed by the execution path and the API justification. 'from ChatGPT, Claude or any AI agent' is filler, and the phrase 'Hipcamp's official API: Hipcamp has no public API' is awkwardly constructed.

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 guidance tool with no output schema, the description covers purpose, return shape, execution path, and rationale. The only gap is that it does not say what happens with the guide's content or whether it is Hipcamp-account-specific versus static.

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 there is nothing to disambiguate and the baseline is 4. The description could have noted that because no inputs are accepted, the guide is generic and pricing details must be supplied later in the browser flow, but its absence is not a serious gap.

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 states a concrete resource (pricing in the user's Hipcamp account) and, crucially, redefines the verb: the tool returns step-by-step instructions (screens, buttons, fields) rather than performing the change. That read resolves the mismatch with the imperative name 'update pricing'. The one residual ambiguity is that the opening sentence reads like a mutation before 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 an explicit workflow: call this first to get instructions, then execute with the cotlet_browser_* tools in the Hipcamp Cloud Browser. It also explains why browser automation is necessary (no public API). It stops short of naming when-not conditions or alternatives such as hipcamp_sync_calendar or cotlet_app_guide.

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