List Cardano DeFi venues

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

The readOnlyHint annotation already signals safety, and the description adds meaningful context by stating 'Read-only: returns index data, not live chain state.' This clarifies that results are from the index, not a live chain query, which is valuable beyond the annotation.

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 tight sentences, front-loaded with the core purpose, then filter options, then an important read-only qualifier. No wasted words or redundant repetition of schema 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?

For a simple list tool with 4 optional parameters, full schema coverage, and a readOnlyHint, the description provides enough to invoke it correctly: what it lists, which filters exist, what free-text query searches, and what the data scope is. No output schema exists, but the nature of a venue list makes the return shape largely predictable.

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%, so the baseline is 3, and the description adds value by expanding on the parameter meanings: it lists venue category types, explains what 'asset' refers to, and specifies that 'query' searches id, name, description, and assets. This complements rather than repeats the schema.

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 states a specific verb and resource: 'List the indexed Cardano DeFi venues' with concrete category examples. This clearly distinguishes list_venues from singular sibling tools like get_venue.

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 conveys clear usage context: it is the collection-listing tool with optional filters for category, asset, capability, and free-text query. It does not explicitly name alternatives or exclusions, but the list-oriented framing makes when-to-use unambiguous.

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