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

Annotations already set readOnlyHint=true, so the tool's read-only nature is clear. The description adds no extra behavioral details beyond listing filters; it does not mention pagination, sorting, or caching, which are present in the schema. No contradiction with 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?

A single well-formed sentence delivers the core purpose and key filter types without redundancy. Every word adds value, making it optimal for quick scanning.

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 18 parameters, 0% schema coverage, and no output schema, the description is too sparse. It omits essential information such as required parameter 'campground', pagination parameters, sorting, and the return structure. A more detailed description is needed to compensate for the lack of schema descriptions.

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?

Schema description coverage is 0%, so description must compensate. It mentions filter categories (type, hookups, accessibility, availability, loop) which partially map to schema parameters, but many parameters (e.g., page, sort, per_page, vehicle_length) are not addressed. The grouping helps but is insufficient for full parameter understanding.

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 clearly states the tool lists campsites for a campground and enumerates filter categories (type, hookups, accessibility, availability, loop), distinguishing it from siblings like campsites.get (single site) and campgrounds.search (campground search).

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?

The description implies usage when needing a filtered list of campsites within a campground, but does not explicitly contrast with alternative tools or provide when-not-to-use guidance. The filter list gives some context but lacks completeness.

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