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

Annotations already cover readOnly, idempotent, non-destructive and closed-world, and the description adds substantial behavior on top: the two return shapes (sourced answer with source URL and checked date vs. direct answer plus top hotels and page URL), the grounding constraint that only published page content is returned, and the exact matched=false fallback. This is exactly the kind of value-beyond-annotations the dimension rewards.

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?

Front-loaded with the routing purpose, then each subsequent sentence carries distinct information: return shapes, grounding rule, failure mode, exclusions. No filler or repetition, and no sentence could be removed without losing a behavior an agent needs.

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?

An output schema exists, so return values need not be spelled out, and the annotations cover the safety profile; the description nonetheless covers input intent, both success shapes, the failure shape, and hard topic limits. Nothing needed to select or invoke this tool correctly is missing.

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% with an example, so the baseline is 3. The description still adds meaning by specifying that the question is plain-language and must name either a hotel or a place, and by clarifying which question topics will not match, which shapes what a caller should put in the single parameter.

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?

States a precise verb and resource: routing a plain-language LA hotel question to the published Journeyed page that answers it, and it explicitly distinguishes the two question shapes (named hotel vs. place). It never names or contrasts sibling tools like search_hotels or hotels_near, so an agent must infer the boundary, keeping it short of a 5.

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?

Gives clear context for when it applies (plain-language questions answerable from published pages) and explicit exclusions (cannot answer about room prices, availability, or guest reviews), plus the no-match behavior. It stops short of naming an alternative tool for those excluded cases, so the 'when not to use' guidance is only partial.

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