geckoterminal_get_networks

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

With no annotations, the description must disclose behavior itself. The phrase 'Get all' is at odds with the paginated page parameter in the schema—there is no mention that results are paginated or that multiple pages may be needed. It also doesn't describe the return format or any limitations.

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 sentence with no filler or repetition, efficiently conveying the core purpose in minimal words.

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 list tool, the description is mostly adequate, but it lacks critical context about pagination behavior and does not clarify how the optional page parameter affects the 'all' claim. Given no output schema or annotations, this missing information leaves the agent uncertain about how to retrieve the complete list.

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 fully documents the single page parameter, and its description is straightforward. The tool description adds no additional semantic meaning about how pagination interacts with 'all networks', so it stays at the baseline for full schema coverage.

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 uses the specific verb 'Get' with the resource 'all blockchain networks' scoped to 'supported by GeckoTerminal', making the tool's primary function clear. It does not explicitly differentiate from sibling tools like geckoterminal_get_dexes or dex_get_networks, but the resource and scope are unambiguous.

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?

There is no guidance on when to choose this tool over alternatives such as get_supported_networks or dex_get_networks, nor any mention of pagination or use cases. The description simply states what it does without context.

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