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

Annotations already declare readOnly=true, destructive=false, openWorld=true, so the safety profile is covered. The description adds real behavioral detail beyond that: the summary flag defaults to summary records without line items, and the GET /api/v2/item endpoint is named. It omits rate limits or response shape, keeping it below a 5.

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?

Two dense sentences with no filler, front-loading what the tool does and what it returns before the filtering options and the endpoint. Every clause carries information.

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 11-optional-parameter list tool with no output schema, the description covers the returned fields, the summary-vs-full behavior, and location-based quantities. It leaves pagination mechanics (start/max_results) to the schema, which is acceptable, but a fuller note on paging behavior would close the gap.

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 all 11 parameters are already documented, establishing a baseline of 3. The description's parameter enumeration ('filter by free text, SKU, category, type, tags, ids or update time') and the location note mirror the schema rather than adding syntax or semantics beyond it.

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 ('List or search inventory items') and enumerates the fields returned (SKU, type, quantities, prices), which is more than a name restatement. The plural scope makes it distinguishable from sosinventory_get_item in the sibling set.

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 clear usage context: use filters for free text/SKU/category/type/tags/ids/update time, and 'pass location to see quantities at one location.' It does not explicitly route to alternatives (e.g., use get_item for a single item or list_reference_data for categories), so no exclusions are stated.

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