get_supported_markets

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

Annotations already declare readOnlyHint=true and idempotentHint=true, which is reinforced by the description's wording 'List'. The description adds that it returns addresses and underlying assets, which is helpful. No contradictions. However, no mention of network filtering behavior or response format.

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 of 14 words, directly describing the tool's purpose. No fluff or redundant information. Front-loaded with the key action 'List all available JustLend lending markets'.

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 the simplicity of the tool (1 optional param, no output schema), the description is adequate but lacks context about how it differs from similar sibling tools like get_all_markets or get_markets_from_api. Could be more complete by noting this is the canonical way to list supported markets.

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 100% for the single optional parameter 'network', which is already described in the schema. The description does not add any additional meaning beyond the schema's definition. Baseline score of 3 is appropriate.

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?

Clearly states the tool lists all available lending markets (jTokens) and specifies that it includes addresses and underlying assets. This is a specific verb+resource combination that distinguishes it from similar tools like get_all_markets or get_market_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?

No guidance on when to use this tool vs. alternatives. There are multiple sibling tools for retrieving markets (e.g., get_all_markets, get_markets_from_api), but the description does not explain why an agent should choose this one. No usage context or constraints provided.

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