accor_search

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

No annotations are present, so the description must carry the behavioral burden. It explicitly states what is excluded (booking, rates, rooms, reviews, loyalty, payment flows) and what is included (static identity, location labels, ratings, source URLs). This goes beyond a simple claim and informs the agent of scope. However, it does not mention pagination or response format, which are minor gaps.

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 sentences, front-loaded with the core purpose and then scope. Every sentence adds necessary information without redundancy, making it efficient and easy to parse.

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 no output schema, the description provides a reasonable preview of the result contents (static identity, labels, ratings, URLs) but does not detail pagination or field structures. For a search tool with eight parameters, the description covers the main use case and limitations, though it could mention paging behavior explicitly.

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?

Parameter schema coverage is 100%, so the description adds limited value beyond confirming the filter set. It clarifies that the query is for a destination or hotel name, which slightly enriches the schema's 'Destination or hotel query' but does not add syntax or format details for the filters.

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 and resource ('Search Accor hotels') and describes the search index and query modes (destination or hotel name). It also lists the filter dimensions, making it distinct from sibling tools like accor_property or accor_search_details.

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?

Implies usage by describing the search functionality and filters, but does not explicitly state when to prefer this over alternatives like accor_search_details or accor_search_suggest. No exclusions or conditions are given.

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