Audit inventory documentation

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

The annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the 'local mirror' scoping and the missing-fields focus, but does not disclose output shape, pagination, or whether results are exhaustive; that is acceptable given the 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?

A single sentence that front-loads the core purpose and includes the important local-mirror qualifier. It is concise with no filler, though 'selected claim-documentation fields' is slightly imprecise.

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?

With no output schema, no parameter descriptions, and sibling tools that also operate on inventory records, this description does not give an agent enough to invoke the tool confidently or interpret its result. It conveys purpose but omits how the parameters map and what the returned records look like.

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 coverage is 0% and the description does not explain receiptField, requirePhoto, or requireValue. 'Selected claim-documentation fields' only vaguely gestures at the parameters, leaving the agent to guess what each boolean controls or what a valid receiptField value looks like.

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 names a specific action ('Find item records missing...') and a resource ('item records') with a scope qualifier ('in the local mirror'). It is clear enough to stand apart from generic search/list siblings, though it doesn't explicitly contrast with them.

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 wording implies this tool is for auditing documentation completeness rather than normal search, but it never states when to prefer it over search_inventory or list_contents. No exclusions or alternative routing are provided.

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