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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the description doesn't need to restate safety. It adds valuable behavioral context by describing the output as interactive cards plus a link to the full guide, and by clarifying this is an editorial ranking rather than exhaustive search 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?

The description is compact and well-structured: it defines the tool, gives usage guidance, and provides a concrete example. The only minor redundancy is repeating the 'curated/editorial ranking' idea in both the first and second sentences, but overall every sentence earns its place.

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 simple read-only tool with two parameters, full schema coverage, rich annotations, and an existing output schema, the description is complete. An agent can correctly select the tool, build the arguments from the example, and understand what kind of response to expect.

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 schema already provides full descriptions for both parameters, so the baseline is 3. The description adds value by mapping a concrete natural-language example to the parameter values ('destination Turkey, focus splash'), which helps an agent translate user intent into correct arguments.

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 returns SplashScout's curated, ranked 'Best family hotels/campsites in [destination]' guides, with an overall version or focus-specific versions. It distinguishes itself from search by emphasizing editorial ranking over general search results.

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 explicitly advises 'Prefer this over search for best X in Y questions' and explains why, which gives clear usage context. However, it refers to 'search' generically rather than naming the sibling search_family_hotels, and it doesn't state when the search alternative might be preferred.

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