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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds genuine value beyond that: it discloses the per-day fields returned, the meaning of includeResources, and the underlying endpoint (GET /v1/listings/{listingId}/calendar), giving the agent a concrete mental model of the payload.

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?

Front-loaded with the resource scope, followed by returned fields, the includeResources hint, and the endpoint. Dense but each clause earns its place; the raw endpoint reference is the only marginally extraneous element.

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 read-only tool with no output schema, the description adequately characterizes the returned data (status values, pricing, stay constraints, notes) so the agent knows what it gets. Minor gaps remain around pagination/range limits, which for a date-bounded calendar call are low-risk.

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%, so baseline is 3, but the description goes beyond the schema by explaining what includeResources actually surfaces ('the reservations occupying each day') rather than the schema's generic 'attached sub-resources'. The date-range parameters are still only defined by 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?

States a specific verb and resource ('Day-by-day availability and pricing for one listing over a date range') and enumerates exactly what is returned (status, nightly price, min/max stay, CTA/CTD, notes). This is clearly distinguishable from siblings like hostaway_get_listing and hostaway_update_calendar.

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 scoping ('one listing over a date range') and the includeResources hint, but there is no explicit when-to-use/when-not guidance or named alternative (e.g. how it differs from hostaway_get_listing or hostaway_calculate_price). Minimum viable rather than routing guidance.

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