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

Annotations already establish that this is a read-only, non-destructive, closed-world operation. The description adds useful behavioral context beyond annotations: the owner must be signed in and the date range cannot exceed 31 days. It still does not explain the exact return shape, such as whether results are counts per room type per night.

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 two short sentences with no wasted wording, and the core purpose is front-loaded. The second sentence adds the key constraints without burying the main point.

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 simple two-parameter read-only tool, the description covers the essential purpose, auth prerequisite, and date-range limit. It is slightly incomplete because there is no output schema and the description does not specify the return format or timezone assumptions.

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 coverage is 100%, and the schema already documents that from and to are YYYY-MM-DD dates. The description adds the 31-day range limit, which is useful, but it does not add syntax or meaning for the individual parameters beyond the schema. The phrase 'by room type' appears to describe output grouping rather than a parameter and is not clarified.

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 states a specific resource and scope: rooms free each night by room type for a date range up to 31 days. It is clear what the tool returns, but it does not explicitly distinguish itself from related siblings such as stays, stay, or house_inventory.

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?

Usage is implied by the availability purpose and by the stated constraints: owner sign-in is required and the range is capped at 31 days. However, the description does not say when to prefer this tool over related siblings or when not to use it.

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