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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the negation 'Does not modify, allocate, receive or ship stock' largely restates them, though it adds useful domain-specific framing. It does not cover behavior for invalid or missing IDs, or the implications of openWorldHint=true (live Infoplus data, possible latency or auth failures).

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 short sentences, zero filler. The positive capability statement comes first and the negative scope clarification follows, which is the right ordering.

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 only one parameter, full schema coverage, and no output schema, the description carries the return-value burden well by naming the fields returned (quantities, lots, location IDs). Nothing an agent needs in order to invoke it correctly is missing.

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 100% and the single record_id parameter is fully documented with a pattern and provenance note ('from a search result'). The description repeats the 'numeric record ID' concept without adding format, sourcing, or error semantics beyond what the schema provides, so 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 specific verb (Read) and resource (inventory detail) and enumerates the returned content: stock quantities, lots, warehouse location IDs. The phrase 'by its Infoplus numeric record ID' implicitly separates it from the search_* siblings, but no sibling is named explicitly.

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?

Usage is only implied: an agent can infer this is the lookup-by-ID counterpart to infoplus_search_inventory, since the tool requires a record ID from a prior search. There is no explicit statement of when to prefer this over the search tool or what to do when the ID is unknown.

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