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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered structurally. The description's 'does not modify, allocate, receive or ship stock' adds domain-specific reassurance about inventory side effects, but says nothing about behavior on a missing/invalid ID or about the response shape.

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 with zero filler; the capability and the returned fields are front-loaded before the scope disclaimer.

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?

A simple single-parameter read tool with full annotations and complete schema coverage, and the description lists what comes back. Only gap is the absence of any note about lookup failure or how to obtain the ID, which matters slightly given no output schema exists.

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?

Only one parameter, and the schema fully documents it at 100% coverage including the numeric pattern and that it comes from a search result. The description echoes 'Infoplus numeric record ID' without adding format, sourcing, or error semantics beyond the schema — baseline 3 for schema-covered params.

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 (Infoplus item) and enumerates the fields returned — SKU, status, packaging, reorder metadata — keyed by numeric record ID. The 'by its Infoplus numeric record ID' framing implicitly separates it from infoplus_search_items, 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: the agent must infer that this tool applies once a record ID is known, and the ID's provenance ('from a search result') lives in the schema, not the description. The negative clause rules out stock actions but never names infoplus_search_items as the way to obtain an ID.

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