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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description usefully adds what the result set contains (drop-in vs near equivalents from other makers, plus companion parts), but says nothing about result ordering, limits, or how 'near' is determined.

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 no filler, and the core result content is front-loaded. The trailing 'plus parts it is commonly paired with' clause is slightly buried but still earns its place.

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 must convey the return shape, and it does so only at a high level. The distinction between drop-in and near equivalents is named but never defined, which matters for interpreting results of a matching tool.

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 0%, so the description must carry the load. It explains that lens restricts by origin and that id identifies the source part, but it does not decode the enum values (cn, not-cn, us, usmca, allied) or clarify whether 'any' is the default.

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 names a specific verb and resource — finding drop-in or near equivalents for a part from other makers, plus commonly paired parts. That scope is distinct enough from a generic search, though it never names search_parts or compare_parts as the contrasting sibling.

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 states the optional origin-lens restriction, which implies the constraint is available but not mandatory. There is no explicit when-to-use guidance versus search_parts or compare_parts, and no statement of when this tool is the wrong choice.

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