List SCAPS files

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is fully covered. The description adds nothing beyond that: no pagination behavior, no indication of whether listing is recursive or shallow, no note on ordering. A 3 is appropriate given annotations carry the burden.

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?

One front-loaded sentence that names the resource first. The trailing 'and more' is vague and adds little, but overall there is no wasted text.

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?

Safety and return shape are handled by annotations and the output schema, so the essentials are present. However, for a paginated listing tool the description should at least acknowledge limit/offset behavior and the scope of what 'folder' means; those gaps leave the agent relying on the schema alone.

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 coverage is only 50%: kind and contains are documented, but limit and offset have no descriptions. The description's folder list merely restates the kind enum and does not explain pagination semantics or how contains interacts with listing, so it fails to compensate for the coverage gap.

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?

States a specific verb (List) and resource (files in a SCAPS data folder), then names the folder categories covered. It is distinguishable from write/run siblings like scaps_write_data and scaps_run_script, though it does not explicitly contrast with read-ish siblings such as scaps_results or scaps_status.

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 never says when to use this tool versus scaps_results, scaps_status, or scaps_describe_device, nor any prerequisites. Only the folder enum loosely implies usage; there is no explicit when/when-not guidance.

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