dex_get_multi_prices

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It mentions 'batched' and 'efficient' but does not disclose return format, pricing currency, rate limits, or potential errors. This is a significant gap for a tool with no annotation support.

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 concise sentences with no filler. The first sentence states the primary function, and the second provides a use case. Perfectly structured for quick parsing.

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?

The tool is simple with two parameters and no output schema. The description gives a high-level overview but lacks details about the response structure (e.g., prices in USD or token-sorted). Given the absence of output schema and annotations, the description is not fully complete but adequate for a basic price fetch tool.

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 description coverage is 100% for both parameters, so the schema already documents them clearly. The description adds no additional meaning beyond the schema, staying at the baseline of 3. It does not clarify token address format or network ID standards beyond what the schema provides.

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 clearly states the tool gets batched prices for multiple tokens on a specific network. The verb 'Get' and resource 'batched prices for multiple tokens' are specific, and the network scope is a distinguishing factor. However, it does not explicitly differentiate from similar sibling tools like get_multiple_prices or defi_get_token_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?

The description implies usage context by stating it's 'Efficient for portfolio valuations,' which suggests when to use it. However, it does not provide explicit guidance on when not to use it or alternatives, so the usage guidance remains implied rather than explicit.

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