koios_address_utxos

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

No annotations are present, so the description carries the full burden. It discloses only that it fetches a UTxO set, omitting behavior around pagination (limit/offset), ordering, extended data (_extended), and the meaning of 'set.' This minimal disclosure is insufficient for an endpoint with 6 parameters.

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 short sentence with no wasted words, but it is under-specified for the tool's complexity. It achieves brevity but sacrifices necessary context, so it is not fully appropriate in size.

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's 6 parameters, lack of annotations, and absence of an output schema, the description is incomplete. It doesn't explain return structure, pagination behavior, or the distinction from similar sibling tools, leaving significant gaps for an agent.

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 a baseline of 3 applies. The description repeats the _addresses concept ('given addresses') but adds no additional meaning beyond the schema descriptions for limit, offset, order, select, and _extended.

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 resource ('UTxO set') with scope ('for given addresses'), making the core function clear. However, it doesn't explicitly differentiate among sibling address-related tools like koios_address_outputs or koios_credential_utxos.

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 koios_address_outputs or koios_utxo_info. It only states the basic action, with no context about prerequisites, use cases, or exclusions.

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