list_oracle_capabilities

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

With no annotations, description carries full burden. It describes the return value (JSON array of objects) and implies a read-only, nondestructive operation. It mentions price information, adding transparency. Could benefit from explicitly stating no side effects, but sufficient.

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?

Concise, no fluff. Front-loaded with purpose, then usage guideline, then return format, then example. 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?

Given zero parameters, an output schema exists (as per context), but description already supplies return format and example. It is complete: explains what the tool does, when to use it, what it returns, and how to call it. No gaps.

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?

Zero parameters, schema coverage 100% (empty). Description does not need to add parameter info. It adds value by explaining the return format and providing an example, which is more than baseline for 0-param tools.

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 uses specific verb 'List' and clearly states the resource: every oracle tool with its AIMarket capabilityId and per-call price. It distinguishes from sibling tools (like ask_oracle, compute_vdf) which perform specific actions, while this tool provides a catalog.

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?

Explicitly says 'Call this first to discover what's available and what each call costs before invoking.' Provides clear context for when to use the tool, though it does not explicitly specify when NOT to use it. The recommendation is strong enough.

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