get_token_market

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. It reveals the data source (GeckoTerminal) and implicitly frames this as a read-only 'view', but does not explicitly state safety, error behavior, rate limits, or permissions. This is moderate transparency for a simple market lookup.

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 two sentences long, front-loaded with the core purpose and output list, followed by input guidance. Every sentence contributes relevant information with no redundancy.

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 single-parameter tool with no output schema, the description provides the key return fields and input formats. It omits explicit response formatting and failure cases, but still gives an agent enough context to invoke the tool correctly.

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?

Although the schema already covers the 'token' parameter with 100% completeness, the description adds valuable nuance by explaining that a ticker like 'TSLA' resolves to 'TSLAx', a behavior not mentioned in the schema. It also confirms both accepted input types.

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 tool's purpose: retrieving a market view of a tokenized stock with specific data fields (price, 1h/24h change, market cap, pool liquidity, 24h volume) via GeckoTerminal. This distinguishes it from siblings like list_markets and get_token_supply by focusing on a single token's market metrics.

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 when to use this tool (for market data of a specific token) and explains acceptable inputs (ticker or contract address), but it does not explicitly contrast with sibling tools or state when not to use it. No alternatives or exclusions are mentioned.

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