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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered structurally. The 'no reservation is created' clause adds domain-specific reassurance that a camping contact lookup will not book anything, but the description says nothing about freshness of the data, caching, or what happens on a failed lookup.

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?

One short clause with the substantive content (what you get) placed first and the negative side-effect note second, so nothing is buried. It is a fragment rather than a sentence, which slightly blunts the opening but wastes no words.

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 zero parameters, no output schema and annotations covering the safety profile, the only real burden is telling the agent what comes back, and the description enumerates contact details, location, day-use hours and overnight hours. That is sufficient for an agent to call it confidently and use the result.

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 and there is no parameter meaning for the description to carry. Nothing in the description conflicts with the empty, fully closed schema.

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 names the specific resources returned: contact details, location, and day-use/overnight hours. That is enough for an agent to tell it apart from siblings like get_camping_price_table or list_camping_offers, though it uses a noun phrase rather than an explicit verb and never names those siblings.

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?

Usage is only implied: the payload (contact info, location, hours) makes the when-to-use case self-evident, and 'no reservation is created' implies this is informational rather than transactional. There is no explicit statement of when to prefer this over the sibling tools or any prerequisites.

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