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

readOnlyHint=true already establishes this is a safe read, so the description doesn't need to restate that. It adds useful context about what each returned entry contains, but says nothing about pagination, result limits, or behavior for properties without pricing periods configured.

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 substantive content. The trailing 'Hostfully: GET /api/v3.3/pricing-periods' is mildly redundant but compact and does hint at the upstream contract.

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 carries the burden of describing returns; it names the fields but doesn't explain the shape (per-date entries, ordering, gaps for unpriced dates). Adequate for a simple three-param read, but leaves the agent guessing about result structure.

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% (property_uid, from, to all documented with types and YYYY-MM-DD patterns), so the baseline is 3. The description's phrase 'one property over a range' loosely maps to the params but adds no format or constraint detail beyond the schema.

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 the specific resource and scope: nightly price, minimum stay, and check-in/check-out availability for each date of one property over a range. It clearly conveys what data is retrieved, though it doesn't explicitly differentiate itself from siblings like hostfully_get_property_calendar or hostfully_calculate_quote.

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?

No guidance on when to choose this over hostfully_get_property_calendar or hostfully_calculate_quote, and no stated prerequisites or conditions. The agent must infer usage from the name alone.

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