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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds genuinely useful behavior beyond them — the 12-month lookback window on sessions, the meaning of the session_status enum values, currency for prices, and the data_freshness recency signal. It does not mention rate limits or payload size, but that is minor for a read-by-id tool.

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, all load-bearing: payload contents first, then the temporal scoping caveat, then the freshness signal and id source. No filler and the most important constraints arrive before any optional detail.

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 no output schema, the description does the work of describing the return payload field-by-field (description, organizer, rating, sessions, prices, registration_status, bookability, data_freshness). Combined with a fully documented single parameter and existing annotations, an agent has everything needed to call and interpret this tool.

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 single camp_id parameter is documented in the schema including its provenance from search_camps. The description restates that provenance but adds no format or constraint detail beyond the schema, which is the baseline case.

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 uses a specific verb and resource ('Get the full profile of one camp') and then enumerates exactly what the profile contains: description, organizer, parent rating, sessions with dates/prices/registration_status/bookability. This distinguishes it cleanly from search_camps (which returns ids) and from get_sessions_and_availability (session-level only).

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 states the prerequisite source ('Use the camp_id returned by search_camps') and a needed pre-check ('check session_status ... before recommending'). It does not say when to prefer the sibling get_sessions_and_availability over this tool when only session data is needed, so the routing guidance is clear but not exhaustive.

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