Create Reservation

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

Annotations are basic (readOnlyHint false). Description adds that it's manual and mentions creating a new guest if inline data provided, but doesn't detail side effects (e.g., reservation creation triggers, permissions). No contradictions.

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 clear sentences (English and Spanish) front-loaded with key info. No unnecessary words; every sentence contributes meaning.

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?

Covers input requirements well, including optional parameters. Has output schema (not shown) for return values. Could mention that reservation ID or confirmation is returned, but overall sufficient.

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%, baseline 3. Description clarifies the relationship between guestId and guest (mutually exclusive options) and notes that currency defaults to workspace currency, adding value beyond 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?

Clearly states 'Create a new reservation manually (not via channel sync)' with specific verb and resource, and distinguishes from sync operations. Lists required fields immediately.

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?

Explicitly says 'not via channel sync' and lists required parameters (propertyId, dates, guestCount). Indicates optional guestId vs inline guest data, but lacks explicit when-not-to-use or alternatives beyond sync context.

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