list_recent

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 states a read-only 'List' operation and the category filter, but does not explicitly mention that it doesn't modify data, how items are ordered (beyond 'recently'), or any default limit behavior (though the schema covers the limit default). This is adequate but lacks some behavioral detail.

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 that front-loads the action and resource, then adds the optional filter. No filler or redundant content.

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?

For a simple 2-parameter list tool, the description and schema together provide sufficient information for an agent to select and invoke the tool. The only gap is that there is no output schema, and the description doesn't specify the return structure, but it does clearly say what items are listed, so this is a minor 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?

The schema already has 100% coverage for both parameters (limit with default and max/min; category as single filter). The description adds only example categories, which is helpful but not critical. Since the schema provides full parameter semantics, the description doesn't need to add much, so a 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 uses a specific verb ('List') with a clear resource ('recently saved Bucket items') and includes an optional category filter with examples. It distinguishes itself from siblings like search_bucket, get_item, and download_video by focusing on list/recent behavior.

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 clearly implies when to use this tool: to list recently saved items, optionally filtering by category. It doesn't explicitly name alternatives or state when not to use it, but the context is clear enough for an agent to choose between list_recent and search_bucket or get_item.

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