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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the description's safety burden is low. It adds substantive context by enumerating exactly what data will be returned (accommodation types, payment terms, reviews), which helps agents predict the response shape. 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?

The description is a single dense sentence that front-loads the core promise and then lists contents in a readable sequence. It is efficient and free of fluff, though a bulleted list would improve scannability slightly given the many items enumerated.

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?

Without an output schema, the description thoroughly documents the return value, covering descriptions, photos, check-in times, season, accommodation types with prices and rules, optional extras, booking questions, payment terms, and reviews. This is sufficient for an agent to correctly invoke the tool and interpret its result, leaving no critical gaps.

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 coverage is 100% and the schema already specifies that 'campsite' is a slug from search_campsites. The description adds only minimal reinforcement that it targets 'one campsite' rather than multiple, which is a marginal semantic improvement over the structured data.

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 'Full details of one campsite' with an explicit verb-implied resource, making it clear this is a read operation for a single campsite's detailed information. The enumerated content (photos, times, prices, reviews) clearly distinguishes it from sibling tools like search_campsites, check_availability, and get_quote, which serve different purposes.

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 use when an agent needs comprehensive details about a specific campsite after obtaining a slug via search_campsites. However, it does not explicitly state when to use this tool versus alternatives or provide any exclusion criteria, so usage guidance is only implicit.

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