unlock_more_data

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

Describes key behaviors: returns upgrade ladder and checkout links, session binding, immediate effect on next call, and pricing tiers. No annotation contradictions. Provides comprehensive behavioral context.

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?

Description is detailed but front-loaded with purpose and usage. Every sentence adds value, though pricing details could be condensed. Structure is logical and scannable.

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?

Despite no output schema, the description explains the return structure ({plans, human_message, what_unlocks}). Covers all necessary context: when to use, behavioral effects, pricing, and alternative. Complete for the tool's complexity.

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?

Single optional parameter 'reason' is well-explained, adding context about helping the human understand the upgrade need. Schema coverage is 100%, but description adds meaningful usage guidance beyond 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?

The description clearly states the tool's purpose: to unlock full data when a preview or locked tool is encountered. It uses specific verbs and resources, and distinguishes from sibling tools like claim_free_key.

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 states when to use (preview result, locked tool, want complete dataset) and provides an alternative (claim_free_key for free tier). Offers clear decision support.

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