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

Annotations already establish that this is a safe, idempotent read operation. The description adds meaningful domain behavior beyond annotations: returned texts, characteristics, devices, exploded views, markers, and documents retain provenance, and observed content or historical relations do not constitute human qualification.

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 purpose and scope are front-loaded in the first sentence, and the second sentence carries important provenance caveats. It is appropriately compact overall, though the second sentence is dense with domain-specific jargon and a long list of content types.

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 a single-parameter read tool with a full output schema and complete annotations, the description provides enough context to invoke and interpret it correctly. The provenance and qualification caveats cover the main interpretive risk.

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?

The single product_id parameter is fully documented in the schema, and the description adds useful validity context by noting that PIDs may include historically public products that are no longer for sale. This meaningfully supplements the schema's active-catalog framing without replacing 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?

The description states a specific verb and resource: reading the current public Nitech product by PID. It also clarifies scope by including out-of-sale products that were historically public, which helps distinguish it from search-oriented siblings such as search_products.

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 clear from the required PID-based retrieval model and the explicit inclusion of historically public out-of-sale products. However, it does not explicitly route the agent to search_products when the PID is unknown or name alternatives for document-specific retrieval.

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