get_supported_dexs

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

With no annotations, the description must convey behavioral traits. The verb 'List' implies a read-only operation, which is basic transparency. However, it does not disclose any additional behaviors such as error handling, rate limits, or what constitutes a 'supported' DEX, so it carries only the minimal burden effectively.

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, front-loaded sentence with zero wasted words. It immediately communicates the tool's purpose without unnecessary detail.

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 simple tool with one optional parameter and no output schema, the description and schema together provide sufficient information for correct invocation. The description clearly states what it does, and the schema explains the parameter. It lacks mention of return format, but that is not essential for a low-complexity listing 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?

The input schema already provides 100% coverage with a detailed description of the 'network' parameter, including examples and defaults. The description text adds no meaningful parameter semantics beyond the schema, so it stays at the baseline 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 'List all supported DEXs on a specific network' uses a specific verb and resource, clearly indicating the tool's function and scope. However, it does not explicitly distinguish itself from sibling tools like 'dex_get_network_dexes' or 'geckoterminal_get_dexes', which likely serve a similar purpose.

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 provides no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, exclusions, or alternative tools, leaving the agent without context for selection among the many DEX-related siblings.

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