redeem_points

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

No annotations provided, so description carries full burden. It discloses that setting confirm=true completes the redemption and requires user confirmation. Also notes that false/omit returns award rates. Lacks mention of side effects (e.g., irreversible booking), but adequate.

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, no fluff. Essential warning is front-loaded. Highly efficient structure.

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?

No output schema, but description hints return of award rates. Does not describe response format for booking phase (confirm=true). Adequate for a simple tool but could be more 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 has 100% coverage for 6 parameters. Description adds emphasis on confirm warning and hints about roomCode (lowest-points option). Adds marginal value over schema, meeting baseline expectation.

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 the tool books a hotel stay using points and shows award rates. It distinguishes from sibling tools like search_hotels and get_room_options by specifying points redemption and two-phase behavior.

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?

Provides explicit instruction: 'Set confirm=true only after getting explicit user confirmation.' Also implies two-phase use (view rates then confirm). Does not compare to alternatives directly, but offers clear context for when to proceed.

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