getSettlementRecord

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

No annotations are provided, so the description carries the full burden. It discloses potential latency during extreme volatility and clear date range behavior, which is helpful. However, it does not mention authentication, rate limits, pagination behavior, or what happens with large result sets.

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?

The description is well-structured with bullet points and a note. It is front-loaded with purpose. However, the volatility note could be integrated into the rules or placed at the end. Still, it is reasonably concise for the information provided.

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 no output schema, no annotations, and 6 parameters, the description is incomplete. It thoroughly explains time range behavior, but omits parameter details (symbol, limit, cursor) and return format. An agent would need additional documentation to use this tool effectively.

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 0%, meaning the input schema provides no descriptions. The tool description only mentions the 'category' parameter (linear) and implicitly the time range parameters through the rules. It fails to explain 'symbol', 'limit', 'cursor', or format of time parameters (e.g., Unix timestamp). This leaves the agent guessing.

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 it queries session settlement records for USDC perpetual contracts (linear). It specifies the scope (USDC contracts) and distinguishes from other query tools by the type of data (settlement records). However, it doesn't differentiate from other 'get' tools that might also return historical data.

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?

The description provides detailed time range rules and latency warnings, but does not explicitly state when to use this tool vs alternatives. Usage context is implied by the tool's purpose, but there is no guidance on scenarios where other tools might be preferred.

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