pons_price

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the data source (DexScreener) and that the price is 'live', which is useful, but it says nothing about freshness guarantees, rate limits, caching, or failure behavior when the token/pair isn't listed.

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?

A single front-loaded sentence that names the resource and its return contents with no padding. It is efficient, though it compresses source and chain details into a trailing clause.

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 and no annotations, the description must carry more, and it does list what is returned (price, liquidity, top DEX pairs). However, it omits the response shape and edge-case behavior, leaving some gaps for a data-fetch 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 tool takes no parameters, so the schema carries nothing to interpret; the baseline for a zero-parameter tool is 4. No parameter semantics are needed or missing.

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 names a specific verb (Get) and resource (live PONS token price, liquidity, top DEX pairs) plus the chain (Robinhood Chain) and data source (DexScreener). It is clear what the tool returns, though it never contrasts itself with the potentially overlapping sibling pons_token_info.

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 statement of when to call this versus pons_token_info or pons_launch_market, which plausibly surface overlapping market data. The fact it takes zero parameters implies a simple read, but no explicit usage context or exclusions are provided.

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