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

Annotations only cover readOnly/openWorld; the description adds real behavioral detail beyond them: which figures are returned with datasheet page references, that missing figures are labelled 'not in the record', that internal estimates are named but never numeric, and that the caller-asserted labelling depends on user_request. Exact-match matching behavior is also disclosed.

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?

The purpose and return contents are front-loaded, and the exclusions follow logically. It is dense and slightly long for a two-parameter lookup, but nearly every clause carries distinct information (returned fields, degraded-data behavior, exclusions).

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 fully carries the return-value burden: it enumerates the returned fields, explains datasheet page references, and describes how incomplete records and estimates appear. Nothing needed to call or interpret the result 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%, so both parameters are already documented in the schema, including the exact-match caveat and the user_request verification purpose. The description adds no further syntax or format guidance for them, 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 ('look up') and resource (an RF component in the validated catalog by manufacturer part number) and immediately scopes it against the full datasheet. It is trivially distinguishable from the design_/run_ siblings, none of which retrieve catalog parts.

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 an explicit trigger ('Use this whenever the user names a specific part, so answers come from catalog data rather than recall') and explicit exclusions ('It does NOT hold derating, absolute-maximum ratings, bias, test conditions or footnotes: for those, read the datasheet link'). Both when-to-use and where-to-go-otherwise are stated.

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