Sync Direct Cost Line Items

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

The annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false) are consistent with the description's claim of creating/updating. The description adds valuable behavioral context: concurrency limitations, field selection priority (wbs_code_id over cost_code_id), and the fact that only supplied fields are changed. 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 overly long and contains redundant/inconsistent statements (e.g., 'update an existing Direct Costs' conflicting with the topic of line items). It includes the full API path and method, which could be shortened. Not every sentence earns its place; the description could be much more concise and clear.

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 mentions 'returns the modified object on success'. It covers required parameters, field selection rules, concurrency, and partial update behavior. However, the inconsistency about Direct Costs vs line items creates confusion, and the description does not clarify whether the 'updates' array can handle multiple items or how errors are reported beyond the 409 conflict.

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?

Input schema has 100% coverage, but the description adds important parameter semantics beyond the schema: the condition that either wbs_code_id or cost_code_id and line_item_type_id are required when creating, and that wbs_code_id takes precedence if both provided. Also clarifies that only supplied fields are changed (partial update). This adds significant value.

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 states it 'creates or updates a batch of Direct Cost Line Items', which clearly identifies the verb and resource. However, later it contradicts itself with 'Use this to update an existing Direct Costs' and 'Updates the specified Direct Costs', confusing line items with direct costs. This inconsistency hurts clarity.

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 some usage guidance: it explains required field conditions (wbs_code_id or cost_code_id + line_item_type_id) and concurrency behavior (no concurrent requests, 409 conflict). However, it does not explicitly differentiate this tool from other sync tools among siblings, and the conflicting statements about updating 'Direct Costs' vs 'Direct Cost Line Items' undermine the guidance.

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