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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered. The description adds genuine behavioral context beyond that: it names the categories of returned content and warns against over-generalizing one variant, which is a real behavioral constraint on how results should be interpreted.

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 tight sentences with the return content front-loaded, then the ID prerequisite, then the interpretive caveat. No filler, though the phrasing is slightly terse and could be marginally clearer.

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?

No output schema exists, so the description carries the return-value burden and does so by listing the content types. Given a read-only 2-param tool with a required enum identifier, this is nearly complete; only sibling alternatives are unaddressed.

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 50% — 'language' is documented in the schema, but 'product' has none. The description partly compensates by telling the agent the ID must come from list_products and be exact, which explains the otherwise bare enum. It does not describe the enum values themselves or the language parameter.

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 ('product') and enumerates the content returned: description, technical tables, source documents, caveats. An agent knows roughly what comes back. It does not explicitly distinguish itself from the sibling compare_products, so it falls short of a 5.

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?

Gives a real prerequisite ('Use exact product ID from list_products') and a caveat ('Never generalize one variant to an entire family'). However it never addresses when to choose this over compare_products or find_material, so usage is implied rather than fully specified.

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