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

The annotations declare only destructiveHint=true. The description adds valuable behavioral context beyond that: it blocks the calendar, syncs to connected channels, restricts accepted channelId values, and mentions overbooking protection is always left on. It does not explicitly state irreversibility or auth requirements, but the side effects are disclosed clearly.

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 five tight sentences, front-loaded with the core action and side effects, followed by channel constraints, pricing guidance, overbooking note, and endpoint. Every sentence earns its place with no redundancy.

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 complex 28-parameter mutation with no output schema, the description supplies the most critical operational context: side effects, channel constraints, pricing prerequisite, and overbooking behavior. It does not describe the return value or auth requirements, but given the lack of output schema and rich input schema, it is largely complete for correct invocation.

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 the baseline is 3. The description goes beyond raw schema by explaining how to populate totalPrice (use hostaway_calculate_price's total) and by emphasizing the accepted channelId values. This adds decision-relevant meaning for two key parameters among 28.

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 verb and resource: 'Create a new reservation on a listing.' It also names the tool's side effects (blocks calendar, syncs to channels), which distinguishes it from siblings like hostaway_update_reservation and hostaway_get_reservation. An agent can immediately tell what this tool does.

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 gives clear prerequisite guidance: call hostaway_calculate_price first and pass its total as totalPrice. It also constrains channelId values and notes overbooking protection is always on. However, it does not explicitly state when not to use this tool or name alternative creation paths beyond the pricing prerequisite.

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