digikey_get_part_details

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

No annotations provided, so description carries full burden. 'Fetch' implies read-only behavior, and listed contents give some idea of expected output. However, missing details on authentication, rate limits, or error handling for invalid identifiers.

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?

Description is a single well-structured sentence that front-loads the tool's purpose and key outputs. However, it could be slightly expanded to cover parameter details without losing conciseness.

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?

Although the output schema may cover return values, the description is inadequate for the tool's complexity (3 parameters, one nested). It lacks parameter guidance and usage context, leaving gaps for the AI agent.

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%, and description does not explain any of the three parameters (identifier, quantity, requirements). It does not state that identifier expects a DKPN or MPN, nor does it describe quantity or the complex requirements object.

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?

Description clearly states the tool fetches authoritative DigiKey product details for a DKPN or MPN, listing included data (pricing, availability, links, normalized parameters, evidence metadata). This distinguishes it from sibling tools like search or comparison tools.

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?

Description implies usage context (when you need detailed product info for a specific identifier) but does not explicitly state when not to use or mention alternatives. Sibling tools are listed but not compared.

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