Update Unit Of Measure

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

Annotations already indicate a write operation (readOnlyHint=false) and non-destructive behavior (destructiveHint=false). The description adds that it returns the modified object, which is useful but not critical. It does not disclose side effects, authorization needs, or error conditions, but annotations cover the safety profile adequately.

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?

Two sentences plus API reference (Procore API, endpoint) with no redundancy. Front-loaded with purpose, then details. Every sentence adds value.

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?

No output schema, but the description mentions the return object. All required parameters are covered. Lacks explanation of validation, error handling, or prerequisites, but for a simple update tool, this is largely sufficient.

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?

Input schema covers all 4 parameters with descriptions (100% coverage). The description lists required parameters but does not add new semantic meaning beyond the schema. Baseline score is appropriate as schema does the heavy lifting.

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 it updates UOM attributes, using the verb 'update' and specifying the resource 'Unit of Measure'. It distinguishes from sibling tools like create_unit_of_measure and delete_unit_of_measure by emphasizing modification of existing records.

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 Units of Measure records,' indicating the correct scenario. It lists required parameters, providing operational guidance. However, it does not explicitly exclude creation or deletion, nor provide alternatives.

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