koios_asset_list

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Get a list of all native assets' and fails to mention pagination behavior, response format, rate limits, or that the list could be large. This is a minimal disclosure that adds little beyond the purpose.

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 concise sentence that front-loads the action and resource. Every word contributes meaning, and there is no fluff or repetition of schema details.

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 tool simply lists all native assets, the description lacks important context about pagination (limit/offset are present in schema but not described), potential result size, and what 'all native assets' entails. Without an output schema or annotations, the one-sentence description is insufficient for complete operational understanding.

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?

The input schema provides comprehensive descriptions for all four parameters, so the description need not add parameter details. However, the description itself adds no extra semantic context about how parameters like 'order' or 'select' affect the list, keeping this at the baseline of 3.

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 tool gets a list of all native assets on the Cardano blockchain, using a specific verb and resource. It conveys the scope with 'all' but does not explicitly differentiate from sibling tools like policy_asset_list, which could be an alternative for filtering by policy.

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 no guidance on when to use this tool versus alternatives such as policy_asset_list or asset_info. It only states what the tool does, leaving the agent to infer usage from the name and siblings.

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