run_bom_review

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it says nothing about side effects, permissions, return values, or whether it modifies state. This is a complete lack of transparency for what appears to be an execution tool.

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?

While the description is extremely short, it is under-specified to the point of uselessness. It is a fragment rather than a functional description, and brevity here sacrifices all meaning, making this more than just concise.

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?

Despite having an output schema, the description gives no indication of what the tool returns or how it fits into a workflow. With many BOM-related sibling tools, this description fails to position the tool's role or provide any operational context.

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?

The schema has one optional parameter 'path' with 0% description coverage, and the description does not explain its meaning or format. The agent is left to guess whether 'path' refers to a file path, object path, or something else, with no help from the description.

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 'BOM review profile' is a noun phrase that essentially restates the tool name without a clear verb or action. It doesn't specify what running a BOM review entails or distinguish it from siblings like review_bom or compare_bom_to_design.

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 provided on when to use this tool versus alternatives. There is no mention of prerequisites, intended use cases, or exclusions. The description offers no actionable context for selecting this tool.

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