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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety and scope are clear. The description adds meaningful behavioral context beyond annotations: it explains that similarity is computed from pre-computed embeddings combining review text and structured attributes, which helps the agent interpret results.

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 tightly written sentences with zero waste. The core purpose is front-loaded, and the second sentence adds useful mechanism without padding.

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?

Given the read-only annotations, full output schema, and complete parameter descriptions, the definition is nearly self-sufficient. The main gap is the absence of sibling differentiation against search_campgrounds, which slightly hinders tool selection despite the otherwise complete picture.

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 description coverage is 100%, so the baseline is 3. The description adds conceptual meaning to the semantic_weight and structured_weight parameters by explaining that embeddings combine review text (semantic) and structured attributes (amenities, terrain, activities), clarifying what those weights control beyond the schema's terse descriptions.

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 a specific verb (Find) and resource (campgrounds similar to a given campground), and adds the method (vector embedding similarity). It distinguishes itself from a generic search by requiring a target campground, but does not explicitly name the sibling search_campgrounds to sharpen the contrast.

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 gives no guidance on when to use this tool versus alternatives like search_campgrounds. There are no exclusions, conditions, or named alternatives; the agent must infer usage entirely from the purpose statement.

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