get_markets

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

With no annotations, the description carries the full burden. It discloses the data fields returned and the optional symbol filter, but does not mention side effects, read-only behavior, pagination, or error conditions. The 'List' verb implies a read operation, but this is not explicit.

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?

A single sentence that front-loads the primary action 'List DorkFi lending markets' and immediately provides the key output details. No redundant or irrelevant words.

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 straightforward list tool with only two parameters and no output schema, the description adequately covers purpose and output. It could mention that 'chain' is required or note the absence of pagination, but the simplicity makes this minor.

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 100%, so the baseline is 3. The description adds minimal value beyond the schema, only restating the optional symbol filter. It does not explain the 'chain' requirement or elaborating on parameter formats.

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 the tool lists DorkFi lending markets with live data including rates, deposits, borrows, and prices. The plural 'markets' distinguishes it from the sibling tool 'get_market', and the optional filter by symbol adds 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?

The description implies this tool is for listing multiple markets, but it does not explicitly contrast with alternatives like 'get_market' for a single market. It provides no when-to-use or when-not-to-use guidance, leaving differentiation to inference from sibling names.

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