Create Purchase Order Contract Line Item

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

The description adds behavioral context beyond annotations by noting that a budget line item will automatically be created for non-budgeted line items under certain conditions. It also states the HTTP 201 response. 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 adequately sized but contains redundancy (repeating 'Creates a new Commitments' and starting with the full name). It front-loads the action, but some sentences could be streamlined for better conciseness.

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 no output schema, the description only states the return type generically ('returns the created object'). It includes a useful note about budget line items. However, it omits details about response structure and potential errors, leaving some gaps for a creation tool.

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?

While schema coverage is 100% with descriptions, the line_item parameter is a loosely defined object with additionalProperties true. The description merely lists required parameters without explaining the expected structure of the line_item object, which could lead to incorrect usage.

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 Purchase Order Contract Line Item', specifying the verb and resource. It provides the API endpoint and mentions 'Commitments' context. However, it does not explicitly differentiate from sibling tools like create_commitment_contract_line_item, leading to some ambiguity.

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 implies usage by stating 'Use this to create a new Commitments in Procore', but it does not explicitly tell when to use this tool versus alternatives. No exclusions or when-not-to-use guidance is provided.

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