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

Annotations already declare the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=true), so the description is not the sole carrier here. It does add the required OAuth scope, which is real value beyond the structured fields, but says nothing about partial-update semantics or what happens to omitted fields.

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 short sentences, no filler; the operation and target are front-loaded and the authorization requirement follows immediately. Nothing needs trimming.

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 5-parameter mutation with a fully-described schema and annotations covering idempotency and destructiveness, the description covers identity, action, and auth prerequisites. It could have noted that this is a partial update, but nothing essential to a correct call is missing.

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%, so all five parameters, including the UUID pattern for id and the ISO 8601 format for completed_at, are already documented in the schema. The description adds only 'by ID', which the schema already implies.

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?

States a specific verb and resource (update a compliance record) plus the identifier used to target it, and 'existing' distinguishes it from create_compliance_record. It does not differentiate itself from the many other update_* siblings in the registry, which is the only gap.

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 supplies a concrete prerequisite ('Requires compliance_records:write scope'), which tells the agent whether it is authorized to call it, but gives no when-to-use guidance or pointer to alternatives such as update_compliance_item or update_compliance_pm_schedule.

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