market_prices

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

No annotations provided and description only says 'Fetch market prices' implying a read operation. Lacks disclosure of pagination, rate limits, or data format, which is necessary given no annotation coverage.

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?

Single sentence of 7 words, very concise but may be too brief given the lack of detail. Could be expanded minimally to improve usefulness without becoming verbose.

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 tool with no output schema and no parameters, the description is minimally adequate but does not help the agent understand what data is returned or how to interpret results, especially among many sibling tools.

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?

Input schema has zero parameters, baseline is 4. Description adds no extra parameter meaning, but no parameters exist to document.

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?

Description states 'Fetch market prices from the EVE Online API' which is a clear verb+resource, but lacks specificity on scope (e.g., region, item) and does not differentiate from sibling tools that also fetch data.

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?

No guidance on when to use this tool versus alternatives like get_region_history or region_orders. Does not address prerequisites or limitations.

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