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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the endpoint and the shape of a returned line (location, lot, quantities), but says nothing about volume, pagination behavior, or ordering — modest added context on top of 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?

Front-loaded with what the resource is, followed by the filter example and endpoint — three compact fragments, no filler. Slightly fragmentary rather than fully sentence-structured, but nothing is wasted.

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, the description carries some burden for describing returns; it partially discharges this by listing line fields, but gives no sense of result volume, default ordering, or paging behavior (left to the schema). Adequate but thin for a list endpoint with no return schema.

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 rql, pgnum, and pgsiz are fully documented in the schema. The description's rql example (`itemIdentifier.sku==SF-Box-DG`) is a domain-specific illustration not in the schema, but it does not explain semantics the schema lacks. Baseline 3 applies.

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 concrete resource ('inventory detail lines') and names the fields they carry (location, lot, quantities), plus the underlying endpoint GET /inventory. It does not explicitly distinguish itself from close siblings such as extensiv_list_stock_details or extensiv_list_stock_summaries, so an agent must infer the difference.

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 gives a filtering recipe with a concrete rql example, which implies how the tool is used, but it never says when to choose it over the inventory-adjacent siblings (stock details vs stock summaries) or whether filters are optional. Usage is implied rather than stated.

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