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

The readOnlyHint annotation already declares this is a safe read operation. The description adds the endpoint and facet (VolatileAsset), which is useful, but it does not describe pagination behavior, result shape, or search limitations beyond what the schema and annotations already cover.

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 extremely concise and front-loaded: one sentence defines the search syntax, followed by the endpoint and facet. Every element earns its place with no wasted wording.

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 simple two-parameter read-only search tool with complete schema coverage and annotations, the description provides enough to invoke it correctly. The main remaining gap is that without an output schema it does not describe the result format, though the tool name and search semantics make the return type reasonably clear.

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 both parameters are already documented in the input schema. The description restates the search parameter syntax but adds no meaningful detail beyond the schema, including no additional context for the page parameter.

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 states a specific verb and resource: searching inventory items by name, item number, or identification number. It clearly distinguishes this as a search operation rather than a general list operation, though it does not explicitly differentiate from siblings like list_inventory or search_assets.

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 description implies usage through the accepted search syntax, but it gives no explicit guidance on when to use this tool versus list_inventory, filter_assets, or search_assets. There are no exclusions or alternative-routing instructions.

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