get_markets

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly states that no API key is required and restricts results to 'active' markets, which are important behavioral traits. It does not mention return format or pagination, but the read-only nature is implied by 'List' and the simplicity of the tool.

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 exactly two short sentences, front-loaded with the primary action and outcome. There is no filler or redundancy, achieving maximum conciseness.

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 zero-parameter public list tool, the description is fairly complete: it states what is listed, the fields of interest (rates and liquidity), and the auth requirement. It lacks an explicit output schema or mention of pagination, but the simple scope makes it adequate for an agent to select and invoke correctly.

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?

The tool has zero parameters, so the schema already covers everything. The description does not need to add parameter details and appropriately focuses on the tool's behavior, aligning with the baseline for zero-parameter tools.

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 'List' with a clear resource 'active lending markets' and additional detail 'with current rates and liquidity'. This distinguishes it from other get_* tools like get_token_price or get_loan_health, which focus on different 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 phrase 'No API key required' provides clear context on when this tool can be used, indicating it is a public access point. However, it does not explicitly contrast with alternative tools or state when not to use it, so it falls short of offering full when/when-not guidance.

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