Create A Change Order Change Reason

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

Annotations already indicate a write operation (readOnlyHint=false). The description adds that it returns the created object on success (HTTP 201), but does not disclose permissions, rate limits, or side effects. It provides minor added value 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 four sentences, but the second and third sentences are repetitive ('Use this to create...Creates a new...') and contain an error ('Change Orders' vs 'Change Order Change Reason'). It could be 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 three parameters with full schema coverage, annotations present, and no output schema, the description provides basic contextual completeness. However, it does not explain the purpose of a change order change reason or when to set 'show_in_select'. The confusion in the description also detracts from completeness.

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?

All three parameters have descriptions in the schema (100% coverage), so the description adds no additional meaning. It merely restates 'Required parameters: company_id' which is already marked in schema. Baseline 3 is appropriate.

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 a 'Change Order Change Reason' but then confusingly says 'create a new Change Orders' which contradicts the resource name and endpoint. While the verb and resource are somewhat clear, the inconsistency reduces 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?

No explicit guidance on when to use this tool versus alternatives (e.g., similar create tools for change orders or reasons). Only the endpoint and required parameter are provided, leaving the agent without context for selection.

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