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

No annotations are provided, so the description must carry the behavioral disclosure burden. It lists output content categories but does not state whether the call is read-only, whether it returns current or historical data, how it validates input, or what the response structure looks like.

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 compact and front-loads the core resource identity. It uses a scannable list of data categories with no filler, though it is telegraphic and lacks a complete sentence structure.

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, the schema and description together cover the input and the general content areas. However, with no output schema, no annotations, and no sibling-routing guidance, the description is only minimally sufficient for an agent to select and invoke it correctly in a crowded toolset.

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 input schema covers the single parameter fully, including an example ticker and the alternative of a 0x address. The description adds no additional parameter semantics beyond what the schema already provides, so the baseline score of 3 applies.

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 identifies the resource as 'One official RHJ stock token' and enumerates the data aspects it covers: bid/ask vs AMM premium, stock/USDG LP pools, meme legs, and correlated/bridge pairs. The purpose is inferable, but there is no explicit verb such as 'get', 'query', or 'analyze', and it does not explicitly differentiate from siblings beyond naming the resource.

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 about when to use this tool versus alternatives. With 40 sibling tools all sharing the talon_ prefix, an agent cannot tell whether talon_stock, talon_lp, talon_premium, or talon_data is the right choice without additional context.

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