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

Annotations already signal that this is a write operation (readOnlyHint=false), non-idempotent, and non-destructive; the description adds the useful nuance that it creates either a new BOM or a new BOM revision. However, it does not describe side effects such as whether passing bom_id updates an existing BOM, whether a revision is auto-created, or what happens when bom_id is omitted.

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 dense sentence with the action verb up front and no filler or repetition. It is appropriately sized for the little information it provides, though that brevity contributes to the completeness gap.

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?

This is a complex mutation tool with 7 parameters, nested item schemas, several enums, and an output schema, yet all behavioral and usage guidance is compressed into one sentence. It does not clarify when to pass bom_id versus create a fresh revision, how source_artifact_id works, or how dependencies are structured, making it incomplete for the tool's complexity.

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%, so the description needs to compensate, but it only broadly maps to items and dependencies via content-type names. Key parameters such as bom_id, project_id, build_quantity, and source_artifact_id are left unexplained, as are important item subfields like line_number, quantity_per_assembly, and make_or_buy.

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 states a specific action ('Create a BOM or a new BOM revision') and names the supported content types: assemblies, catalog items, custom parts, services, consumables, artifacts, and interface dependencies. It is clearly distinct from the read-only get_bom sibling, though it does not explicitly contrast with other BOM-related 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?

No guidance is given for when to use this tool versus alternatives such as get_bom for reads or validate_project for validation. The only implied usage signal is the verb 'Create', so the agent is left to infer the appropriate context.

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