Get Src20

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

With no annotations, the description carries the behavioral burden. It goes beyond a simple data list by warning that 7d/30d/total volume are often 0 or null due to upstream exchange behavior, and explicitly cautions against misinterpreting zero as 'no trading'. This is valuable, non-obvious behavioral context.

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 well-organized: a lead sentence conveying scope, a parenthetical breakdown of returned data, and a focused caveat sentence. Each sentence earns its place, and the important zero-volume warning is given prominent placement.

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?

The output schema exists, so detailed return fields do not need repetition. The description sufficiently explains the tool's aggregate nature, the data categories included, and a key data-quality quirk. It could add guidance on finding a tick or behavior for unknown ticks, but these are minor gaps given the simple single-parameter input.

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 0%, and the description only implies that 'tick' identifies the SRC-20 token. It does not explain tick format, case sensitivity, or how to resolve a valid tick. The description should compensate more for the bare schema, but it still weakly ties the single parameter to the tool's purpose.

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 verb and resource: retrieve comprehensive data for one SRC-20 token. It enumerates the specific data groups (deploy record, mint status, market data), which distinguishes it from narrower sibling tools like src20_balance, src20_holders, or src20_market.

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 phrase 'Everything about one SRC-20 token in one call' clearly communicates when to use this tool: when a single token's full picture is needed. It does not explicitly name alternatives or exclusions, but the context is clear enough for an agent to choose this over single-purpose sibling tools.

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