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

Annotations already declare read-only and idempotent, but the description adds traits they cannot express: the truncation flag's meaning, the unavailability and not-found preconditions, and a security-relevant warning that the content is untrusted seller-authored text. That last point is exactly the behavior an agent could not infer from structured fields.

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?

Three sentences, front-loaded with the core action, then the sibling routing, then the edge cases and safety caveat. No sentence is redundant against another, and nothing is padding.

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?

An output schema exists, so return values need not be described, yet the definition still clarifies the truncation field and the named error outcomes. For a single-parameter read tool with full annotation coverage, nothing an agent needs to call 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 'id' parameter already documents the short-ID/UUID forms. The description only implies that the target is one product; it adds no acceptable-format or resolution detail beyond the schema, so the 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 and resource ('Get the root README of the package a buyer currently receives for one Kurodyne product') plus scope details: raw Markdown or plain text, size limit, truncation semantics. It is immediately distinguishable from get_product_files, which returns the full file list.

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?

Explicitly names the triggering condition ('when a recommendation depends on setup steps or usage') and the alternative ('get_product_files for the full list of package files'). It also enumerates the two failure cases and what causes them, which is stronger routing guidance than most definitions provide.

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