koios_asset_summary

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

No annotations are provided, so the description carries full burden. While 'Get' implies a read operation, it does not disclose behavioral traits such as pagination limits, rate limits, error behavior, or side effects. The parenthetical lists return content, not operational details.

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 one concise sentence, front-loaded with the actionable verb and resource. The parenthetical adds relevant clarifying information without waste.

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?

There is no output schema, and the description provides a partial list of return fields, which is sufficient for basic invocation. It does not describe the full return structure or edge cases, but given the tool's simplicity and the rich schema, it is mostly complete.

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 100%, so baseline 3 applies. The description does not add parameter-level details beyond the schema, but the parenthetical hints at what the asset summary contains, which helps infer the role of policy/name parameters.

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 uses a specific verb ('Get') and a clear resource ('summary of a specific asset'), with a parenthetical enumerating key return fields (total transactions, wallets, mints/burns). This differentiates it from sibling tools like koios_asset_info or koios_asset_list by emphasizing a summary view.

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?

There is no guidance on when to use this tool vs alternatives. It does not mention distinguishing scenarios, exclusions, or recommend it for overviews vs detailed history, leaving the agent to infer usage solely from the name.

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