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

readOnlyHint=true already establishes the safety profile, so the description is not carrying that burden. It does add one genuinely useful behavioral detail — the encoding '0 = not available' — but says nothing about rate limits, auth, or edge cases on the date range.

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?

A single sentence delivering resource, return fields, range semantics and multi-property scope, followed by a short endpoint reference. Front-loaded and free of filler.

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?

With no output schema, the description usefully enumerates the returned quantities (nightly price, minimum length of stay, availability per date) so an agent knows what to expect. Parameter coverage is complete via the schema. Only the practical boundaries of the date range and the unit/currency of the price are left unstated.

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%: all three parameters (apartment_ids, start_date, end_date) are documented in the schema, including the yyyy-mm-dd format. The description only restates 'one or more properties' and 'each date in a range', adding no syntax beyond the schema — the baseline 3 applies.

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 ('Get the nightly price, minimum length of stay and availability ... for each date in a range, for one or more properties'), which tells an agent exactly what it returns. It does not differentiate itself from the sibling smoobu_check_availability, which covers overlapping ground, so it stops 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?

There is no statement of when to use this tool versus alternatives such as smoobu_check_availability, nor any prerequisites or exclusions. Usage can only be inferred from the resource being described.

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