Create Direct Cost Item

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

Discloses the 100-line-item limit and the multipart/form-data requirement for attachments, which goes beyond annotations. Annotations (readOnlyHint=false, destructiveHint=false) are consistent; description adds meaningful behavioral context without contradiction.

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?

Description is a single paragraph of 5 sentences, front-loading the purpose and then adding constraints. It includes endpoint info which may be redundant but not excessive. Could be slightly shorter but remains focused.

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?

Describes the return value (HTTP 201, created object) and references the Procore API section. However, it does not explain the nested structure of the 'direct_cost' parameter or the 'attachments' array, leaving some gaps for an AI agent. Given the complexity of nested objects, additional clarity would help.

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?

Adds value beyond the input schema by mentioning the 100-line-item limit and the multipart/form-data requirement for attachments. Schema already covers 100% of parameters with descriptions, so the baseline is 3; the extra details push it to 4.

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?

Description clearly states 'Create a new Direct Cost Item in the specified Project' with specific verb, resource, and scope. It distinguishes from siblings like create_direct_cost_line_item by focusing on the item level, and adds the 100-line-item limit for uniqueness.

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?

Provides clear context: 'Use this to create a new Direct Costs in Procore' and specifies required parameters. However, it does not explicitly differentiate from similar tools like create_direct_cost_line_item or sync_direct_cost_items, or state when not to use it.

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