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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and locality are covered. The description adds relevant behavioral context — that the policy content is informational and the actual signing/payment happens off-platform, so this tool cannot complete a booking. It says nothing about return shape or freshness of policy data.

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?

Two sentences, both load-bearing: the first enumerates exactly what is returned, the second sets the assistant's boundary. Front-loaded with the resource list and no filler.

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?

For a single-parameter read-only tool with no output schema, the enumerated return contents plus the platform/role caveat give an agent enough to call it and to interpret responses. A note on whether policies can be session-specific vs platform-wide would close the remaining gap.

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 sess_id parameter is documented in-schema as coming from search_camps or get_camp_details. The description's 'for one session' merely reinforces that; it adds no format or sourcing detail beyond the schema, so baseline 3 applies.

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?

Specific verb (get) plus an enumerated resource set — refund policy, payment schedule, waiver requirement, platform payment facts — scoped to one session. It reads clearly as distinct from search_camps, get_camp_details, and get_sessions_and_availability, though it never names those siblings explicitly.

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?

'Parents review, sign, and pay on kiddinglab.com — assistants only prepare the choice' gives concrete context on the agent's role and implicitly points to create_booking_handoff as the transactional path. It doesn't spell out alternatives or exclusions, so it stops short of a 5.

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