Create Change Order Package

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

Annotations already indicate readOnlyHint=false (write operation) and destructiveHint=false. The description confirms creation and mentions HTTP 201, but adds no extra behavioral context like authentication needs, side effects, or idempotency beyond what annotations provide.

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 relatively concise with two main sentences plus a list of required parameters and API endpoint info. Minor redundancy ('Change Orders' repeated) but overall efficient.

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 creation tool with a nested object parameter and no output schema, the description is moderately complete. It includes the endpoint and API category but lacks details about the change_order object structure and the exact response fields, which would help an agent understand what to provide and expect.

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 description coverage is 100%, but each parameter's description is generic (e.g., 'unique identifier for the project'). The tool description also lists required parameters but does not elaborate on the structure of the 'change_order' object or provide additional 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 clearly states the tool creates a new Change Order Package, using the verb 'Create' and the resource name. However, it does not explicitly differentiate from sibling tools like update_change_order_package or list_change_order_packages, which are common alternatives.

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 says 'Use this to create a new Change Orders in Procore' and lists required parameters, implying usage context. But it does not specify when not to use it or mention alternative tools for different scenarios, such as updating or listing change orders.

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