dd2_recent_items

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

With no annotations, the description carries the full burden and does substantial work: it discloses sort order (StorageData._UpdateIndex, newest first), the exact fields surfaced, and the key-item tab behavior. It never explicitly states this is a read-only log requiring a running game/bridge, which is the main omission.

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?

A single front-loaded sentence that leads with 'Item log' and the scope, then layers parenthetical detail. Dense with parentheticals but each clause adds information rather than restating the name.

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?

An output schema exists and the description still enumerates returned fields, so return values are well covered. However, for a two-parameter tool with no annotations, leaving the filter semantics of `name` undefined is a substantial hole.

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% and both parameters are undocumented. `limit` is never mentioned, and `name` is entirely unexplained — the description does not say whether it filters by item name or owner, or how it interacts with the 'recent items' scope.

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+resource: the most recently changed inventory entries across player, pawn and stash storages, newest first. The 'recently changed' scope implicitly distinguishes it from the full-inventory sibling dd2_items, but that sibling is never named, so the differentiation must be inferred.

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?

No explicit when-to-use or alternative routing, but the parenthetical 'DD2 keeps no pickup history' functions as a when-not caveat that prevents a common misuse. An agent still has to guess whether to reach for this or dd2_items for a full snapshot.

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