Sync Direct Cost Items

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

Annotations already indicate it modifies data (readOnlyHint=false) and is not destructive. The description adds that it does not support concurrent requests and mentions a special enum value for direct_cost_type. It also says it returns the modified object. This provides some additional behavioral context beyond 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 poorly structured, with what appears to be truncated text ('If there is an attempt to up...') and contradictory statements. It is not concise, mixing multiple ideas in a disorganized manner.

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 tool is a batch upsert with no output schema, the description should explain the item structure, error handling, and success criteria. It only provides a link to 'Using Sync Actions' and basic parameter notes, leaving significant gaps.

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?

Both parameters have descriptions in the schema, so baseline is 3. The description notes that 'updates' is an array of Direct Cost Items, but does not elaborate on the item structure, so it adds limited meaning beyond the schema.

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 Items, which is the core action. However, it later suggests it only updates existing costs, creating ambiguity about whether it also creates. This inconsistency lowers 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 mentions that concurrent requests are not supported, which is a usage constraint, but it does not provide guidance on when to use this tool versus the individual create/update tools. No clear when-to-use or when-not-to-use context.

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