get_markets_from_api

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

Discloses stability advantage and lists specific return fields (APY, TVL, etc.), adding value beyond annotations (readOnlyHint, idempotentHint). No contradictions with annotations.

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?

Two concise sentences, no wasted words. First sentence states purpose, second adds context and return details.

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?

Covers return data adequately for a simple read tool with one optional parameter. Lacks mention of potential errors or limits, but annotations cover safety.

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% and already describes the network parameter. The tool description adds no extra parameter information, so baseline score 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 'Get all market data from JustLend API' with specific verb and resource. Distinguishes from siblings like get_market_data or get_all_markets by emphasizing bulk data from a stable API source.

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?

Provides a clear usage hint: 'More stable than contract queries,' indicating when to prefer this tool. Could be improved by explicitly stating when not to use it or listing alternatives, but the guidance is helpful.

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