add_calculation_line

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

The description implies mutation but does not disclose behavioral traits such as required permissions, idempotency, side effects (e.g., whether it updates item total), or error conditions. With no annotations provided, the description carries the full burden and fails to address these aspects.

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 concise sentence that front-loads the action and includes the formula. It is appropriately brief but could benefit from a bit more detail on parameter usage.

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 11 parameters, no annotations, and no output schema, the description is insufficient. It does not explain the return value, side effects, or connect all parameters to their purpose. The formula covers only the core calculation, leaving many gaps.

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 description adds meaning to count, dim_1, dim_2, dim_3, and deduction by explaining the formula. However, 0% schema description coverage means other parameters like item_id, reference, zone, level, description, and notes are left unexplained. The formula is helpful but incomplete for the full parameter set.

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 tool adds a quantity calculation line to an item and includes the formula (count x dim_1 x dim_2 x dim_3 - deduction). It distinguishes from sibling tools like add_material_cost and create_item. However, it doesn't clarify what 'reference' means, which is a required parameter.

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 on when to use this tool versus alternatives like add_material_cost. It doesn't mention prerequisites (e.g., the item must exist) or when not to use it. The description lacks context for appropriate usage scenarios.

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