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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds value beyond that by disclosing the auth requirement (a Cotlet API key with access to this app) and clarifying what 'base price' means relative to single-night special prices. It still omits return format and pagination behavior.

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?

Purpose is front-loaded in the first sentence and the following sentences each carry distinct information (downstream IDs, price semantics, auth). Slight redundancy from the 'Hipcamp:' prefix and title echo, but nothing is wasted.

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?

There is no output schema, and the description does step in to describe the return shape (every listing with its sites, status and base price). Combined with the auth note and identifier guidance, an agent has enough to call it correctly; only pagination/limits are unaddressed.

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 instead documents the identifiers the response surfaces (listing_id, site_id) and explains the base-price field's semantics, adding meaning without needing to compensate for any schema 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 specific verb and resource (list the host's listings) and enumerates the payload contents: sites, status, and base nightly price. It is fully unambiguous, though it does not explicitly differentiate itself from the other hipcamp read endpoints, so it falls just short of a 5.

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?

'Use listing_id and site_id from each item in the other endpoints' gives implied downstream usage, which is genuinely helpful context. However, it never says when to call this versus alternatives or what prerequisites trigger it, leaving usage only loosely framed.

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