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

With no annotations, the description carries the full burden and does well: it discloses result ordering (newest first), that returned data includes timestamp and actor ('when and by whom'), that deletion is non-destructive to history, and that records are recoverable. Pagination or result-cap behavior is not mentioned, which is the main remaining gap.

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 no filler; the core purpose and scope come first, and the recovery note closes it. Every clause carries information an agent needs.

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 zero-parameter list tool with no output schema, the description covers what is returned (deleted items, actor, timestamp), the ordering, and the recoverability path. Only result volume/pagination handling is left unspecified, which keeps it from a 5.

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 tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly implies no filtering arguments are needed.

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 ('Lists the inventory items that were deleted'), plus scope ('in the user's company') and ordering ('newest first'). This clearly separates it from siblings like get_inventory (active items) and delete_inventory_item (the mutation), and it names restore_inventory_item as the follow-up.

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 pairing with restore_inventory_item gives an explicit reason to call this tool and what to do next, and the 'deleted' qualifier implies you use it instead of get_inventory when looking for removed items. It stops short of an explicit 'use this instead of X when Y' routing statement.

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