Sync Purchase Order Lines

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

Annotations only state readOnly=false, idempotent=true, destructive=false. The description adds enormous behavioral context: the sync (create/update) semantics, the 413 limit, defaulting of company_id/project_id to procore_set_config, the requirement for existing material/header, partial-update behavior, success return value, and common HTTP error statuses (401, 403, 404). No contradictions 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?

Although long, every sentence carries operational value—limits, prerequisites, partial updates, defaults, error handling, and API context. The first sentence front-loads the core purpose, and there is no filler or redundant restatement of the title.

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?

The description is remarkably complete for a complex sync operation: prerequisites, batch limits, partial-update semantics, configuration defaults, error payloads, and success response are all covered. The only gap is the mismatch between the documented input schema and the mentioned body parameters, which could make it harder for an agent to correctly construct a request.

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% for the three required path parameters, each already described as URL identifiers. The description adds useful meaning for id ('must identify an existing parent record — resolve with list tool') and mentions config-based defaults for company_id/project_id, but those defaults conflict with their required status in the schema. It also references body-level identifiers (ids, origin_ids, item_id, item_origin_id) that are absent from the schema, creating ambiguity about how to pass them.

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 opens with 'Creates or updates Purchase Order lines identified using either ids or origin_ids', a specific verb+resource+scope. It clearly distinguishes this sync-line tool from sibling sync/update tools like sync_purchase_order_contracts and update_purchase_order_line_item, and it also names the exact API endpoint.

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 provides solid usage context: the material/header must already exist, the 1000-entity limit triggers a 413, partial updates are encouraged ('Send only the fields you intend to change'), and the parent id should be resolved with a list tool first. However, it does not explicitly name alternative tools or state when NOT to use this tool compared to single-update tools.

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