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

The annotations already declare this is read-only, idempotent, and non-destructive. The description adds useful behavior beyond annotations: it names the required items:read permission, says results are permission-visible, and clarifies that no stock changes occur.

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 compact and front-loaded: it begins with the core read operation, then adds search scope, permission, and safety context. Every sentence contributes useful information without repetition.

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 eight-parameter, no-output-schema tool with 0% schema description coverage, the description is not complete enough to guide correct invocation. It covers the main search and permission model but omits essential parameter semantics and pagination/filtering behavior.

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 0% across eight parameters, but the description only explains q and partially explains location_id. It leaves key parameters such as type, archived, category_id, page, limit, and include_total semantically undefined, so an agent must infer their behavior from names alone.

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 clearly states that this reads a visible inventory page and lists retrievable fields, so the verb and resource are specific. It does not explicitly contrast with the sibling salesbinder_get_item, which is the main nearby alternative for item retrieval.

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 implies use for searching inventory by name, SKU, barcode, serial, or numeric item number, and notes that location filtering changes the result. However, it does not say when to use this tool versus salesbinder_get_item or how to choose among search modes.

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