Get Liqwid market rates

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

Annotations already establish readOnlyHint and openWorldHint, so the read-only claim is expected; however, the description adds meaningful context by stating 'no API key needed,' specifying 'live Liqwid v2' data, and naming the exact data fields returned. No behavioral contradictions with the 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?

The description is two sentences with no filler. The main purpose is front-loaded, followed by authentication context, then the parameter behavior with examples. Every sentence earns its place.

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 simple read-only getter with one optional parameter, the description is complete: it states what data is returned, that it is live, that no API key is needed, and how to filter. The absence of an output schema is mitigated by explicitly listing the returned metrics.

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 documents asset as a case-insensitive display-name filter, so the baseline is 3. The description adds value by giving concrete examples ('ADA', 'iUSD') that illustrate valid asset values, which the schema alone does not provide.

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 opens with a specific verb and resource: 'Read live Liqwid v2 money-market data,' then enumerates exactly what is returned (supply APY, borrow APR, utilization per market). This makes it easy to distinguish from sibling tools like get_quote or get_balance.

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 the tool is for read-only market data and notes that no API key is needed, but it never explicitly states when to prefer this over alternatives or when not to use it. Usage context is clear, but exclusion/alternative guidance is missing.

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