Search Src20

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

With no annotations, the description carries the behavioral burden. It does disclose the returned fields and the meaning of mintable_only=True, which is useful. However, it does not mention read-only behavior, pagination, result limits, or default filtering beyond the schema, leaving some behavioral gaps.

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?

Three sentences, front-loaded with the core purpose, then output fields, then the main parameter behavior. Every sentence adds value, and the description is appropriately sized for the tool's simplicity.

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?

Given an output schema exists, the description does not need to repeat return value structure. The tool has only two parameters and both are semantically covered. It is missing only explicit sibling routing and notes on edge cases, so it is nearly complete for effective invocation.

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%, so the description must explain the parameters. It does: 'q' is a tick fragment and 'mintable_only=True' filters to tokens under 100% progress. This compensates for the schema's lack of descriptions, though it could add detail about matching behavior or result limits.

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 opens with a specific action and resource: 'Search SRC-20 tokens by tick fragment.' It clearly defines what the tool does and lists the returned fields. However, it does not explicitly differentiate itself from sibling tools like get_src20 or list_src20_deploys, so it does not earn a 5.

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 'by tick fragment' implies this tool is for partial-ticker search rather than exact lookup, which gives some usage context. But no alternatives are named, and there is no explicit guidance about when to prefer this tool over related siblings like get_src20 or src20_market.

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