Ordiscan: searchSRC20Tokens

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, which cover safety and idempotency. The description adds no additional behavioral details (e.g., pagination behavior, result limit, or search algorithm), so it meets the baseline but does not enhance understanding.

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 a single sentence, which is concise but too short to convey necessary information. It front-loads the purpose but omits any param or usage details, leading to under-specification rather than efficient communication.

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 the complexity (6 parameters, no output schema), the description is incomplete. It does not explain search behavior, how to use sorting or pagination, or what results look like. The tool lacks output schema, so the description should at least hint at the return structure.

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%, meaning no parameter descriptions exist in the schema. The description does not compensate by explaining the meaning of 'query', 'deployer', 'sort_by', etc. Parameters with enums (sort_by, sort_order) lack usage context. The agent has no guidance on how to construct effective searches.

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 'search' and the resource 'SRC20 tokens', which is straightforward. However, it does not differentiate from sibling tools like 'getSRC20Token' or 'listBRC20Tokens', missing the opportunity to clarify its scope and filtering capabilities.

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 on when to use this tool versus alternatives. The sibling list includes many search tools (e.g., searchCryptoByName, searchEvmTokensBirdeye), but the description offers no context or exclusion criteria.

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