agentscoin_token_info

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and openWorldHint=true, so the safety profile is partly structured. The description usefully adds the cost (0.1 AGENT, a real side effect on the caller's balance) and the data source, but it never explains the destructiveHint or the required privateKey, so meaningful behavioral gaps remain.

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 tight sentence with the core purpose front-loaded and the cost clause appended. No filler, though 'premium data, DexScreener' is slightly compressed to the point of being cryptic.

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 paid, open-world tool annotated as destructive with a required credential parameter and no output schema, the description omits too much: it says nothing about the privateKey requirement, auth expectations, failure modes, or what is returned. An agent cannot call this confidently without guessing.

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 only 50%: 'query' is documented in the schema while 'privateKey' has no description anywhere. The tool description adds nothing about either parameter, so it fails to compensate for the undocumented credential parameter, which is the one an agent is most likely to misuse.

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?

Names a concrete verb ('Look up') and a specific resource ('crypto token price/liquidity'), plus the upstream source (DexScreener). It is distinguishable from most siblings, though it does not explicitly differentiate itself from the adjacent agentscoin_price tool.

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 'premium data... Costs 0.1 AGENT' clause implies a cost tradeoff that shapes when to use it, but there is no explicit when/when-not guidance and no routing against agentscoin_price or agentscoin_network_info, which an agent must infer.

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