geckoterminal_get_pool

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. However, it only says 'Get detailed information' without elaborating on read-only semantics, response format, data freshness, or potential error conditions. This is a significant gap for a tool with no annotation safety net.

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 of nine words, clearly front-loaded with the action and resource. There is no wasted language or redundant 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?

With no output schema, no annotations, and a sparse description, the tool's behavior is under-specified. The description doesn't explain what 'detailed information' includes, how to format the network ID, or any other context that would help an agent invoke it confidently. The wealth of sibling tools adds ambiguity that the description does not resolve.

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% with both parameters described ('Network ID' and 'Pool contract address'). The description's 'by address' reinforces the poolAddress parameter but adds little beyond the schema. Baseline 3 is appropriate because the schema already handles parameter documentation.

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 ('detailed information about a specific pool'), and the method ('by address'). This distinguishes it from related siblings like geckoterminal_get_multi_pools (multiple pools) and geckoterminal_pool_trades (trades).

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. There is no mention of exclusions, alternatives, or specific scenarios. The description simply states what it does without contextualizing it among the many related geckoterminal pool tools.

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