Updates The Specified Transfer Line Item.

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

Beyond annotations, the description discloses partial update behavior ('Send only the fields you intend to change; omitted fields keep their current values'), default values for company_id and project_id, prerequisite that transfer_id and id must reference existing records, success return value, and common error statuses (401, 403, 404). 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?

Each sentence adds value: purpose, update semantics, defaults, return value, error handling, required parameters, and endpoint. No redundant or filler content; the structure is logical and front-loaded with the core action.

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?

For a 10-parameter tool with no output schema, the description is thorough. It covers what the tool does, how to use it (partial update, defaults, ID resolution), what it returns, error scenarios, and the exact API endpoint. Combined with the fully described schema, an agent has sufficient information to invoke it correctly.

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%, but the description adds important semantics: the partial update convention applies to all body fields, company_id/project_id have defaults, and transfer_id/id must be resolved first. This enhances understanding beyond the schema's basic field descriptions.

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 action ('Updates') and the resource ('an existing specified transfer line item in the specified Procore project'). It also specifies the HTTP method (PATCH) and context (Materials Management), distinguishing it from other update tools like updates_a_transfer_document_header or updates_a_line_item_of_a_shipment.

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 practical guidance: resolve transfer_id and id with the matching list tool, company_id/project_id default from procore_set_config, and only send fields to change. It does not explicitly name alternative tools or state when not to use it, but the context is clear enough for correct selection.

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