Booking Reviews

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to mention that this is a read-only operation, whether it can be expensive or rate-limited, or that it supports async execution modes. The description mentions the endpoint but not the behavior around async/sync or webhook usage, which is critical for a potentially long-running operation.

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 concise, just one sentence, but it lacks useful information. It's not overly long, but it could be more informative without becoming bloated. It repeats the endpoint name which is somewhat redundant. Front-loading is fine, but the content is thin.

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 tool's complexity (11 parameters, async execution options, webhook), the description is grossly inadequate. It doesn't explain the business context (e.g., how to use 'query' for Booking URLs, what 'cutoff' means, when to use 'execution_mode'). The output schema exists, so return values are covered, but the description fails to provide enough context for an agent to call this tool effectively, especially with so many optional parameters.

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 has 100% description coverage for all parameters, but many descriptions are terse (e.g., 'Skip reviews', 'Booking sort parameter'). The description text adds no additional meaning beyond what's in the schema, so it doesn't compensate or clarify. Baseline 3 is appropriate as the schema covers the parameters, but the tool description adds no value in clarifying parameter usage.

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 fetches Booking reviews via a specific endpoint, but it's somewhat vague about the exact resource (reviews for what? Booking URLs?). It distinguishes from siblings like yelp_reviews and tripadvisor_reviews, though not explicitly. The verb 'Fetch' is specific and the resource is 'Booking reviews', making it clear enough.

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 provides minimal usage guidance, only mentioning the endpoint. It doesn't explain when to use this tool versus alternatives like tripadvisor_reviews or yelp_reviews. No context on prerequisites (e.g., need Booking URLs) or typical use cases. The agent is left to infer usage from the name and parameters.

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