Inspect a Robinhood Chain token

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds only that it computes a 'small-position exit grade', with no mention of data freshness, chain coverage, or cost; given the annotation coverage this is a marginal but acceptable contribution.

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 with no filler; the read verb leads and the returned data follows. It is efficient, though its brevity is arguably part of why the behavioral and parameter gaps exist.

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, the description usefully enumerates what is returned (pools, liquidity, volume, price, exit grade). But for a tool requiring an address argument it omits the parameter's meaning and format and gives no sense of how results relate to the sibling exit tools, leaving the definition only minimally sufficient.

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 description coverage is 0% for the single required 'token' parameter, and the description never explains it. The address format (0x + 40 hex) and the fact it must be a Robinhood Chain token come only from the title/pattern, not the description, so compensation for the coverage gap is essentially absent.

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 (Read) and a concrete set of resources (pools, liquidity, volume, price, exit grade) for a token, so an agent knows exactly what comes back. It does not, however, distinguish this from the exit-oriented siblings (simulate_exit, compare_exit_sizes, explain_exit_signal), which overlap on the 'exit grade' concept.

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 call inspect_token versus simulate_exit, compare_exit_sizes, or explain_exit_signal. Usage is only implied by the word 'Read', leaving the agent to infer that this is the snapshot/read step that precedes the other exit tools.

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