get_prices

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

No annotations provided, so description carries burden. Discloses that it fetches mark prices from 4 exchanges and allows optional symbol filtering. Missing details like read-only nature or response format, but basic behavior is covered.

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 short sentences, front-loaded with key action, no redundant words. Each sentence provides distinct information: what and how.

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 simple tool with one optional parameter and no output schema, description explains input and output (prices from 4 exchanges). Could mention that it's a read operation, but sufficient for typical use.

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 has 100% coverage for 'symbols' parameter with example and omit option. Description adds value by explaining the cross-exchange and mark price context, going beyond schema details.

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 the verb 'Get', resource 'cross-exchange prices', and scope 'all 4 exchanges'. Distinct from sibling tools like 'get_markets' or 'get_funding_rates' by explicitly mentioning cross-exchange and mark prices.

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?

Implies usage for comparing prices across exchanges via 'for comparison', but no explicit when-to-use or alternatives. Siblings don't include another price fetcher, so it stands alone, but guidance is minimal.

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