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

Annotations already cover read-only, idempotent, non-destructive behavior, so the description does not need to restate safety. It goes further by disclosing the default compact summary shape (identification + summary + weight + cost + publisher/source) and the `detail: 'full'` behavior that expands to the complete document. This adds real behavioral context beyond the structured annotations.

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 three sentences with no filler: scope, use case, and response-shape behavior are each covered concisely. It is front-loaded with the core search purpose before introducing the output detail option.

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 an 8-parameter search tool with no required parameters, full schema coverage, and an output schema, the description provides enough context to select and invoke it correctly. It explains what the tool searches, what the default result shape is, how to get full results, and who is in scope.

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 the schema already documents every parameter, including the `^name$` exact-match syntax, type examples, pagination, and sorting. The description reinforces how `detail` changes the response but does not add meaning beyond what the schema already provides; baseline 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 opens with a clear verb and resource: 'Search the item library the user has access to.' It also names the concrete item categories (weapon, armor, tool, adventuring gear, magic item) and the search dimensions (name, type, ruleset), making it easy to distinguish from sibling search tools like vault_search_characters, vault_search_monsters, vault_search_spells, and vault_search_rules.

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?

It states the intended use case explicitly ('Use this to locate a weapon, armor piece, tool, adventuring gear entry, or magic item...') and clarifies the scope (stock items plus the user's own house items). It does not explicitly name sibling alternatives to exclude, but the domain boundary is clear enough for an agent to route correctly.

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