get_redemption_queue

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

With no annotations provided, the description carries the full burden. It successfully discloses the sorting behavior (max price ascending) and aggregation, but lacks details on what constitutes a 'redemption queue', the return data structure, or any side effects/pagination.

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?

Single sentence with zero waste. Every word earns its place: 'aggregated' distinguishes the tool, 'sorted by max price ascending' reveals behavior, and 'specific iAsset' maps to the parameter. Front-loaded and efficient.

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 single-parameter getter without output schema or annotations, the description adequately covers the core function but lacks explanation of the return value or the domain concept of a redemption queue. Sufficient for basic invocation but incomplete for full comprehension.

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 description coverage is 0%, requiring the description to compensate. It references 'iAsset' which maps to the 'asset' parameter and implies the enum values (iUSD, iBTC, etc.), but does not explicitly describe the parameter name, format, or valid values beyond the implicit reference.

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 uses a specific verb ('Get') and resource ('aggregated redemption queue'), and distinguishes itself from the sibling 'get_redemption_orders' through the 'aggregated' modifier. It also specifies the sorting behavior ('max price ascending'), providing clear scope.

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?

While the term 'aggregated' implies a difference from 'get_redemption_orders', there is no explicit guidance on when to use this tool versus its sibling or other alternatives. No prerequisites or exclusions are mentioned.

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