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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered by structured data. The description usefully discloses that pricing is brand-qualified storefront retail and includes stock/eligibility/link, but says nothing about the limit/pagination behavior implied by the 'limit' parameter or about failure modes for unknown parts.

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?

A single dense sentence with the most important payload (exact part identity) front-loaded and no padding. It is efficient, though the long comma-list of return fields verges on a data dump.

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 does the right thing by enumerating return values (identity, models, price, stock, eligibility, link). However, it omits result-set limits, matching behavior for ambiguous parts, and any distinction from the three sibling lookup tools, leaving the definition only minimally complete.

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 description coverage is 0%: 'part', 'brand', and 'limit' have no documented meaning in the schema. The description only indirectly hints that 'brand' affects the price returned ('brand-qualified') and never explains 'part' matching rules or what 'limit' bounds (results? models?). With zero schema coverage the description should carry this burden and does not.

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 (Return) and a concrete resource set: appliance part identity, recorded models, brand-qualified retail price, stock, eligibility, and product link. This clearly separates it from verify_fitment or lookup_substitution in spirit, though it never names a sibling to make the boundary explicit.

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?

There is no statement of when to use this tool versus lookup_model_parts, lookup_substitution, or verify_fitment. The word 'exact' weakly implies it is not a substitution search, but the agent is left to infer the routing condition entirely.

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