geckoterminal_get_multi_tokens

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states that multiple tokens are fetched in one request and does not describe what 'information' is returned, whether the operation is read-only, error handling, or any rate limits. This is a minimal disclosure.

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?

The description is a single, concise sentence that front-loads the core purpose and key constraint. No redundant information is included.

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 has no output schema, so the description must convey what 'information' is returned, but it does not. It also does not mention response formatting, pagination, or any other contextual details. For a batch token tool, this is insufficiently complete.

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 network and tokenAddresses. The description adds the batch limit but this is also present in the schema (maxItems: 30). Thus, the description adds little beyond the schema, warranting the baseline score of 3.

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 clear verb ('Get') and resource ('information for multiple tokens') with a batching constraint ('in a single request (up to 30)'). It distinguishes from the single-token sibling geckoterminal_get_token but does not differentiate from other multi-token tools like get_multi_token_info.

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 batching (single request, max 30) but provides no explicit guidance on when to choose this tool over alternatives such as get_multi_token_info or dex_get_multi_prices. There is no mention of exclusions or alternative tools.

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