Update A Compliance Document.

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

Annotations already provide readOnlyHint false and destructiveHint false. The description adds that it performs a partial update (PATCH) and returns the modified object. It does not mention permissions or side effects. With openWorldHint true, the description's additional info is helpful but not extensive.

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 concise at four sentences and front-loaded with the purpose. There is slight redundancy between the first sentence and the third ('Updates the specified Commitments and returns...'), but overall it is well-structured and not verbose.

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?

Despite 100% schema coverage, the description lacks context about the relationship between compliance documents and commitments, and the specific contract types (work_order_contracts) is only in the endpoint path. Given the complexity (16 params, many arrays), the description should clarify usage scope and differentiation from similar tools.

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?

The input schema has 100% coverage, so all parameters are described in the schema. The description merely lists the required parameters, which is already evident from the schema. No additional meaning is provided beyond what the schema already conveys.

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 'Update the specified compliance document' and clarifies it updates an existing Commitments. It also provides the API endpoint path, which helps identify the resource. However, it does not explicitly differentiate from the sibling tool 'update_a_compliance_document_project_v1_0', though the endpoint version is implied.

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 update an existing Commitments (only the supplied fields are changed)', which gives usage context. But it does not specify when not to use this tool or mention any alternatives among the many related sibling tools, such as update_requisition_compliance_document.

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