koios_plutus_script_list

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

No annotations are provided, so the description carries the full burden. It only states the basic function and does not disclose pagination behavior, performance implications, return format, or any side effects. For a potentially large dataset of all Plutus scripts, this is insufficient.

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, front-loaded with the core verb and resource. Every word earns its place with no redundancy.

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 tool has 4 optional parameters, no output schema, and no annotations. The description is too terse to fully inform an agent about the response structure, default pagination, or how to use the tool effectively among 100+ siblings. A slightly more detailed description would be warranted given these gaps.

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 all parameters (limit, order, offset, select) are already documented in the schema. The description adds no additional parameter semantics but correctly implies the list can be paginated. Baseline of 3 is appropriate.

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 a list of all Plutus scripts on the blockchain' uses a specific verb and resource, clearly indicating what the tool returns. It distinguishes from sibling tools like koios_script_info (which targets a specific script) and koios_native_script_list (which lists native scripts rather than Plutus scripts).

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, nor does it mention pagination, filtering, or any prerequisites. It is a generic 'get all' statement without context.

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