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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. However, the description adds no behavioral context beyond the bare title: it does not mention rate limits, pagination constraints, how facets behave, or any other operational characteristic. With annotations present, the description still fails to add meaningful value.

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 single sentence is concise and front-loaded, but it is under-specified rather than truly concise. Every word earns its place only in the sense that there are very few words; the brevity comes at the cost of useful detail.

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 tool with 13 parameters, multiple filters, pagination constraints, and an output schema, the description is far too thin. It does not explain what facet aggregation returns, how to interpret facets, or when to use this versus the sibling search/item tools. While the output schema covers return values, the description leaves critical invocation context 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?

The input schema has 100% description coverage across all 13 parameters, including detailed enum values and caveats (e.g., enrichment-derived facets staying empty until coverage is high). The description adds nothing about parameters, so the schema does all the work. Baseline 3 is appropriate when schema coverage is high.

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 'Facet aggregation over the Airbnb markets dataset' essentially restates the tool name and dataset, adding little beyond what the identifier already conveys. It does not specify what a facet is, how aggregation works, or how this differs from sibling tools like datasets_airbnb_search or datasets_airbnb_item. This is closer to a tautology than a clear, specific verb+resource statement.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The description gives no indication of what scenarios call for facet aggregation or why an agent would choose this over datasets_airbnb_search.

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