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

With annotations limited to readOnlyHint and openWorldHint, the description usefully adds the result cap (20 per page, 5 pages) and the fact that rows carry a typical Chase Travel nightly rate and the double-credit flag. It does not disclose filter combination logic, ranking defaults, or rate-freshness caveats.

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 compact sentences, front-loaded with the primary action and scope, with the result constraint tacked on where it belongs. No filler, though the parenthetical collection branding is slightly verbose.

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 10-parameter, zero-required search tool with no output schema, the description covers what the results contain and how many come back, which is the right compensation. It still omits how filters combine and what 'typical nightly rate' means in practice.

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 70%, so structured fields already carry most semantics. The description reinforces the 'double credit' and 'nightly rate' concepts, but adds no syntax or meaning for city/state/country/query/sort that the schema does not already give.

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 specific verb (search) and resource (hotels in The Edit by Chase Travel) and names the scope of the collection, plus what the results carry (nightly rate, 2026 double credit). It is clearly distinguishable from get_edit_hotel (detail fetch) and find_dining_credit_restaurants, though it never names a sibling 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?

No when-to-use guidance and no routing to alternatives, despite four siblings that overlap conceptually (get_edit_hotel for detail, sapphire_reserve_credits for credit questions). The only real guidance is the pagination note, which is about output shape, not tool selection.

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