geckoterminal_get_multi_pools

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

With no annotations provided, the description carries full burden for behavioral transparency. It only conveys that this is a read operation and that up to 30 pools can be queried. It doesn't disclose response format, error behavior, partial failures, or any rate limits, leaving significant gaps.

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, clear sentence with no wasted words. It front-loads the key purpose and batch limit. While it could be slightly more informative without becoming verbose, it is appropriately concise.

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 batch query tool with no output schema and no annotations, the description is too terse. It doesn't explain what pool information is returned, how to format the network parameter, or how errors are handled. This leaves the agent under-informed for correct invocation.

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 coverage is 100%, as both 'network' and 'poolAddresses' are already described in the input schema. The description adds the 'up to 30' limit, which is also present in the schema (maxItems). Since the schema does the heavy lifting, the baseline of 3 applies.

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 verb 'Get' and resource 'information for multiple pools' with a batch limit. It differentiates from sibling tools like geckoterminal_get_pool by emphasizing 'multiple pools' and 'single request'. However, it doesn't specify what 'information' encompasses or explicitly name alternatives, so it's not a 5.

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 is provided on when to use this tool versus alternatives like geckoterminal_get_pool or batch pricing endpoints. Its usage is merely implied from the description, with no explicit mention of when it should be preferred or excluded.

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