koios_asset_addresses

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

With no annotations, the description carries the full burden for behavioral transparency. It merely states 'Get all addresses' and does not disclose pagination behavior, ordering, or any caveats about what 'all' includes (e.g., zero-balance addresses). No additional context is provided beyond the basic action.

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 that is front-loaded and contains no wasted words. Every word contributes to the core purpose.

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 description is adequate for a simple query tool, and the schema covers parameter details. However, it lacks any contextual information about the response shape, pagination behavior, or typical use cases. Given the absence of an output schema and the brevity of the description, it feels minimally complete but with room for improvement.

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?

All parameters have descriptions in the schema (100% coverage), so the baseline is 3. The description does not add any extra meaning to the parameters beyond what the schema already provides, such as the distinction between _asset_policy and _asset_name.

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 'Get all addresses holding a specific asset' clearly states a specific action (get) and resource (addresses) with a qualifier (holding a specific asset). It distinguishes from sibling tools like koios_asset_utxos (which retrieves UTXOs) and koios_asset_nft_address (which retrieves the address of an NFT).

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 clear context: use this tool to retrieve addresses that hold a given asset. It does not mention exclusions or alternative tools, but the context is unambiguous given the sibling list. A score of 4 reflects clear context without explicit alternative guidance.

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