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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds valuable context about the return structure: pre-computed recommendations across slot types (essential, activity, comfort, amenity_gap) and that each includes product details and purchase links. This goes beyond the annotations and schema, clarifying what the agent can expect.

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 two sentences, front-loaded with the primary purpose, and every clause earns its place. It efficiently communicates the core function, the slot types, and the output contents without any extraneous information.

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?

The tool is simple (2 params, 1 required) and has an output schema, so the description needn't detail return fields. It covers the key aspects: what it does, the slot types, and what results include. It does not mention edge cases like invalid campground IDs, but for a read-only lookup with good schema support, this is comprehensive enough.

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%, so the baseline is 3. The description adds meaning by explaining the slot_type values: essential (must-have), activity (activity-matched), comfort (nice-to-have), amenity_gap (compensates for missing amenities). This is not present in the schema, which only lists the enum-like values without definitions.

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's purpose: 'Get personalized gear recommendations for a specific campground.' It specifies the resource (campground), the action (get), and the output (recommendations). It also differentiates from sibling tools like search_gear and compare_gear by emphasizing the campground-specific, pre-computed nature and listing slot types.

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 context ('for a specific campground', 'pre-computed recommendations') but does not explicitly state when to use this tool versus alternatives like search_gear or build_packing_list. It lacks exclusions or alternative references, so guidance is implied rather than explicit.

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