list_items

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds useful context about what is returned (path, size, mtime) and the 'latest scan' constraint, but says nothing about pagination, empty results, or whether results reflect the most recent scan only.

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?

Two tight sentences with the primary purpose front-loaded and the downstream constraint second. No wasted words.

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?

With no output schema, the description partly compensates by naming returned fields, which is good. But for a tool with 4 parameters and pagination defaults, the lack of any ordering or paging explanation leaves a real gap.

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 0% across 4 parameters. The description only implicitly covers 'category' ('one category'); it says nothing about sort options, limit (max 500, default 50), or offset, leaving the agent to infer pagination and ordering from enum values alone.

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 and resource ('Items found in one category'), scoped to 'the latest scan', and names the returned fields (path, size, last modified). It clearly differs from list_categories, though it doesn't explicitly contrast itself with that sibling.

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 sentence 'Only these exact paths can be passed to move_to_trash' establishes a downstream dependency and implies the tool is the way to obtain trashable paths. However, there's no explicit when-to-use vs list_categories guidance, no mention of needing a completed scan, and no exclusions.

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