deleted_items

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

No annotations are provided, so the description carries full burden. It neither confirms read-only behavior nor discloses any side effects, permissions needed, or rate limits. The only behavioral hint is that 'since' is required, but that's a usage requirement, not a behavioral trait.

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 sentence, which is concise, but it is too sparse. It does not front-load the most critical information for tool selection, such as what makes this tool distinct or typical use cases.

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?

Given the tool's complexity (nested parameter, retrieval purpose) and the presence of an output schema, the description should provide at least a brief overview of what the output contains or how pagination works. It does not, leaving the agent underinformed.

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 description adds no meaning beyond the schema. It does not explain the 'req' parameter or its subfields (e.g., q, since, limit). Schema coverage is 0% at the top level, and the description fails to compensate, despite the sub-schema having some descriptions.

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 states it retrieves deleted items, which is clear but lacks differentiation from sibling tools like trash_items or search_items. It does not specify scope or what 'deleted' means in this context.

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 mentions 'requires since' but gives no guidance on when to use this tool versus alternatives (e.g., trash_items for all trashed items). No exclusions or prerequisites are stated.

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