geckoterminal_get_dexes

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 does not mention that this is a read-only operation, does not explain pagination despite the page parameter, and does not describe the structure of the returned DEX objects. The word 'all' is misleading given the presence of a page parameter.

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, front-loaded sentence with no redundant words. It efficiently and clearly states the tool's core purpose without unnecessary elaboration.

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 the absence of an output schema and annotations, the description leaves important gaps: it does not clarify pagination behavior, the meaning of 'all' in the context of the page parameter, or the shape of the returned data. It is minimally adequate but lacks critical context for fully informed 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?

The input schema already provides complete descriptions for both parameters with 100% coverage, including network ID examples and a page default. The description adds no additional parameter semantics beyond what the schema conveys.

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 action (Get), the resource (all DEXes), and the scope (on a specific network). It effectively distinguishes this tool from siblings like geckoterminal_get_networks, which lists networks rather than DEXes.

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 when the user wants DEXes for a given network, but it provides no explicit guidance on when not to use it or which alternatives exist (e.g., dex_get_network_dexes, get_supported_dexs). There is no comparative context to help the agent select among overlapping DEX-related tools.

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