An item's history

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds ordering (newest first), the pagination signal ("more is true when there are older ones"), and the shape of each entry (when, what in words, who, how). It does not state permissions or rate-limit behavior, but for a scoped read tool that is a minor 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?

Front-loaded with the core statement, then usage, then prerequisite, then return shape — a logical order with no filler. The long parenthetical enumeration of event types is dense but each item earns its place by telling the agent what will appear in the history.

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?

There is no output schema, so the description carries the return-value burden and does so fully: field-by-field entry structure plus the pagination flag. Combined with the named prerequisite and alternative tool, an agent has everything needed to call it correctly.

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 100%, so itemId and limit are already documented with bounds and defaults, which sets the baseline at 3. The description reinforces newest-first ordering and ties the "more" flag to the limit, but adds no new syntax or format detail beyond the schema.

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 ("What happened to one item, newest first") and enumerates the event types covered: adds, edits, photos, warranties, maintenance, stock, loans. It also names get_item as the sibling for current state, so the agent can distinguish the two without opening either schema.

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?

Gives concrete use-case examples ("when did we move the ladder?", "when was the furnace last serviced?"), an explicit exclusion ("for the item as it is now use get_item"), and a prerequisite workflow ("Get the id from search_inventory first"). Nothing about when to reach for this tool is left to inference.

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