get_listing_occupancy

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds only the scope (date range) which is also in the schema. It doesn't disclose return format or edge cases (e.g., handling of empty calendar). With strong annotations, this is acceptable but not enriched beyond them.

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 a single, well-structured sentence that is front-loaded with the action ('Calculate occupancy rate') and states the scope. No filler or redundant information.

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?

This is a simple read-only calculation tool with three fully documented parameters and no output schema. The description is sufficient for most use cases, though it could mention the return format (e.g., percentage) to avoid ambiguity. Given the low complexity, this is nearly complete.

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 each parameter has a description (listingId, from, to). The description adds no new parameter-level detail, only restating the date range aspect. Since the schema fully documents parameters, the baseline of 3 is appropriate.

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 uses a specific verb 'Calculate' with a clear resource 'occupancy rate' and scopes it by 'for a listing over a date range.' This clearly distinguishes it from sibling tools like get_calendar or get_listing_pricing, which serve different purposes.

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 implies clear context: use this when you need occupancy rate for a listing during a specific interval. It doesn't explicitly mention alternatives or exclusions, but the purpose is self-evident from the name and description, so no confusion with siblings.

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