Src20 Holders

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

With no annotations, the description carries full burden for behavioral disclosure. It states the snapshot is at the current block and that results are ordered by amount descending. It does not mention pagination behavior, rate limits, or any potential side effects, but for a read-only snapshot tool these are minor 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?

Two sentences, no filler, with the core behavior first and the use case second. Every word earns its place, and the structure is ideal for quick agent scanning.

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?

An output schema exists, so return-value documentation is covered. The description covers the essential inputs (tick) and the use case, and the pagination defaults are in the schema. For a simple snapshot tool, it is sufficiently complete, though it could mention that the result may be paginated.

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%, so the description must compensate. It clarifies that 'tick' is the SRC-20 identifier, but it does not explain 'page' or 'limit' beyond the schema's defaults. Since these are standard pagination parameters, the lack of explanation is a modest but real gap.

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 verb ('snapshot'), a precise resource ('SRC-20 tick'), and the output ordering ('largest first'). It clearly distinguishes itself from sibling tools like stamp_holders (for stamps) and src20_balance (single-address balance) by focusing on holder distribution for a tick.

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 provides a clear use case ('concentration checks (top-10 share)') which tells the agent when to apply this tool. It does not explicitly name alternatives or exclusions, but the purpose is specific enough to route correctly among siblings.

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