Ordiscan: getSRC20Token

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint, making behavioral traits transparent. The description adds value by listing the specific metadata returned (deploy info, max supply, etc.) and noting case-insensitivity, which complements the annotations without contradiction.

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 consists of two concise sentences: the first states the core purpose and return fields, the second provides context on SRC-20. It is front-loaded and waste-free.

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 simple single-parameter fetch tool with no output schema and strong annotations, the description covers the key information: what it does and what it returns. It could mention error handling or typical ticker format, but the schema already addresses case-insensitivity. Overall, it is sufficiently complete.

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 provides full parameter documentation (100% coverage) with a clear description of the 'tick' parameter. The description reiterates 'by ticker' but adds no new parameter semantics beyond the schema. Baseline 3 is appropriate.

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 specifies the tool's purpose: 'Fetch metadata for a single SRC-20 token ... by ticker: deploy info, max supply, mint progress, holder count, and creator.' It also contextualizes SRC-20 as the Stamps protocol equivalent of BRC-20, distinguishing it from similar tools like getBRC20TokenInfo.

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 description implies usage for a single token by ticker, but does not explicitly contrast with sibling tools like searchSRC20Tokens or getStamp. However, the purpose is clear enough to guide appropriate selection.

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