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

Read-only safety is already covered by readOnlyHint and openWorldHint=false, so the description earns credit for what annotations cannot say: undocumented figures are not invented, and commercial figures are deferred to quoting. It does not describe behavior for an unknown slug or a product with no documented specs.

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 sentences, front-loaded with the verb and the data returned, with no filler. The second sentence is densely packed with three separate constraints, which makes it slightly harder to scan but each clause carries real information.

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 no output schema, the description carries the burden of describing the return payload — and it does, naming specs, images and source. Combined with read-only annotations and full schema coverage, an agent has everything needed to call it correctly.

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?

There is one parameter with full schema coverage, so the baseline is 3; the description lifts it by stating the accepted forms (slug or model) and, crucially, its origin in search_products. It adds no example formatting beyond the schema's own 'dci5800-t8e2' sample.

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?

Specific verb (Get) plus enumerated resources (specifications, images, source) for exactly one product, scoped by slug or model. It also separates itself from both siblings: the slug comes from search_products, and quote-time figures belong to a different path.

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?

It tells the agent where the identifier comes from (search_products) and effectively excludes commercial data by noting prices, lead times, reach and OSNR are confirmed per quote, which points at request_quote. It stops short of an explicit 'use request_quote when you need pricing' directive.

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