digikey_export_order_list

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

No annotations are provided, so the description must disclose behavioral traits. It mentions default filtering and that POSSIBLE_MATCH is 'unsafe', but lacks detail on side effects, authentication needs, rate limits, or what happens to the data. The source of the lines is also unclear.

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 description is concise at two sentences, front-loading the key behavior and format options. It is easy to parse, though could benefit from a brief note on the bom parameter.

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?

Given the complexity of the tool (6 parameters) and missing annotations, the description is insufficient. It does not explain the primary input (bom), output locations, or behavior of mode. The output schema exists but the description still lacks context for many parameters.

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?

With 0% schema description coverage, the description partially compensates by explaining the format parameter (TSV, CSV, JSON, Markdown) and the include_possible_matches parameter ('POSSIBLE_MATCH requires explicit opt-in'). However, it leaves the bom, mode, output_dir, and saved_path parameters undefined.

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 specifies the action ('Export'), the resource ('only VERIFIED_MATCH and VERIFIED_WITH_ASSUMPTION lines'), and the output formats (TSV, CSV, JSON, Markdown). It clearly distinguishes from sibling tools by focusing on exporting an order list.

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?

The description implies when to use (for exporting certain verified lines) and provides a condition ('POSSIBLE_MATCH requires explicit opt-in'), but does not explicitly contrast with sibling tools or give guidance on when not to use this tool.

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