List Src20 Deploys

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

With no annotations, the description carries the full behavioral burden. It discloses the result ordering ('newest first'), the fields included, and the fact that it lists deploy transactions. It does not mention pagination behavior or rate limits, but for a read-only list tool the core behavior is well covered.

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 two sentences with zero filler. The primary purpose and ordering are front-loaded, followed by a compact list of returned fields and then the routing guidance. Every phrase earns its place.

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 return-value details are available structurally. The description covers purpose, ordering, fields, and alternatives. The only notable gap is pagination semantics for the page/limit parameters, which is minor given the schema provides defaults.

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 compensate for the undocumented parameters. It never mentions page or limit, leaving the agent to infer their meaning solely from parameter names and defaults. The description adds no value beyond the input schema.

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 states a specific resource ('SRC-20 DEPLOY transactions'), the ordering ('newest first'), and the exact fields returned (tick, max, lim, decimals, creator, block and time, deploy stamp URL). It also differentiates from related siblings by pointing to src20_market and get_src20, so an agent can tell this tool apart without opening schemas.

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 explicitly gives routing guidance: 'For a ranked market view use src20_market; for mint progress use get_src20.' This tells the agent when NOT to use this tool and which alternative fits those specific needs, leaving no ambiguity about the intended use case.

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