List Quarantined Whatbox Items

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds the human decision-making context, which is useful but doesn't disclose any additional behavioral traits such as output format or filtering capabilities. No contradiction with annotations.

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, compact sentence that front-loads the action and purpose without any unnecessary words or repetition of annotations.

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 is simple, but the complete absence of parameter documentation (rootIndex) leaves a significant gap. There is no output schema, and the description doesn't clarify the return format or what 'items' refers to. The purpose is clear, but operational details are insufficient.

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 schema provides no description for rootIndex (0% coverage), and the description doesn't mention it at all. The agent is left without any explanation of what rootIndex controls, making correct invocation guesswork.

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 action (list), the resource (quarantine directory), and the purpose (so a human can choose to restore or purge). It distinguishes itself from siblings like whatbox_purge_quarantine and whatbox_move_path.

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 implies the use case: listing quarantine items before a human decides to restore or purge. It doesn't explicitly name alternatives or exclusion criteria, but the context is clear enough that an agent would know when to invoke this tool.

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