export_bom

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It mentions exporting to CSV and a manifest, but does not state side effects, whether files are written, output format details, or any access requirements. The term 'bounded resources' is unclear and under-explained.

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 a single sentence with no wasted words, but it is under-specified. The vague 'bounded resources' phrase reduces clarity, making it less effective than a fully self-contained concise description.

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 an output schema exists and the tool has few parameters, the description lacks usage guidance and parameter semantics. Given the large sibling set, it should better locate this tool within the BOM export workflow, but it remains thin.

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 the description does not mention either parameter ('path' or 'include_dnp'). The schema provides titles and defaults, but the description adds no semantic meaning over the structured fields, failing to compensate for the coverage gap.

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 clearly states the verb 'Export' and the resource ('generic UTF-8 CSV BOM and provenance manifest'), distinguishing it from sibling tools like get_bom and export_fabrication_outputs. The phrase 'bounded resources' is somewhat vague but does not obscure the main purpose.

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 explicit guidance on when to use this tool versus alternatives like get_bom or export_fabrication_outputs. The description implies an export use case but provides no exclusions, prerequisites, or context for selection.

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