checkout

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

With no annotations provided, the description fully discloses the critical behavioral difference between confirm=true (charges) and false/omit (preview). It could mention if other side effects occur (e.g., email sending), but the core behavior is transparent.

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, zero waste. The first sentence states the purpose, the second adds the crucial usage rule. Perfectly front-loaded and concise for an AI agent to parse quickly.

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?

Given the complexity (12 params, but only 2 required) and no output schema, the description covers the essential behavior and the critical confirm parameter rule. It could specify what the preview or confirmation output looks like, but it is largely 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%, so baseline is 3. The description adds value by emphasizing the confirm parameter's role, but that is already in the schema's description. Other parameters are not elaborated beyond the schema, so no additional semantic improvement.

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 clearly states 'Complete a Marriott hotel booking' which is a specific verb+resource. It also distinguishes between preview and actual completion based on the confirm parameter, setting it apart from sibling tools like search_hotels or select_room.

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 provides when-to-use guidance with the IMPORTANT note: 'Set confirm=true only after getting explicit user confirmation. Without confirm=true, returns a booking preview instead of charging.' This clearly instructs the agent on the correct usage pattern.

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