Create Work Order Contract Line Item

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

The description adds value beyond annotations by noting the automatic creation of a budget line item for non-budgeted line items, which is a side effect. Annotations already indicate it is not read-only, so the description enhances transparency. No contradiction with annotations.

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 somewhat verbose with redundant statements about 'Commitments' and the return value. It contains information that could be omitted or reorganized for clarity, but it is not excessively long.

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 nested 'line_item' object with no defined schema, the description fails to explain what fields are expected. No output schema exists, and there is no guidance on selecting this tool among siblings. The side effect is mentioned but not fully contextualized.

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 coverage is 100% with parameter descriptions, so baseline is 3. The description reiterates the required parameters but adds no additional meaning about the structure of the nested 'line_item' object, which has open additional properties.

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 'Create a new Line Item in a specified Work Order Contract,' specifying the action (create) and the resource (line item under work order contract). It distinguishes from siblings like 'create_commitment_contract_line_item' by mentioning 'Work Order Contract' explicitly.

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 lacks explicit guidance on when to use this tool versus alternatives like 'create_commitment_contract_line_item' or 'create_purchase_order_contract_line_item.' It mentions the automatic budget line item creation as a note but does not provide when-not-to-use or selection criteria.

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