Create compliance record

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

Annotations already declare the safety profile (readOnly=false, destructive=false, idempotent=false, openWorld=false), so the bar is lower. The description adds a genuinely useful auth requirement (compliance_records:write), but says nothing about non-idempotency consequences, duplicate-record behavior, or side effects on related PM schedules.

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 with the core action front-loaded and the permission requirement second. Efficient, though the parenthetical adds only marginal value and no usage routing is included.

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 seven-parameter mutation tool with five required FK-style references and no output schema, the description is thin. Permission scope is covered, but entity-resolution prerequisites and duplicate handling, which matter for a compliance audit trail, are absent.

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 seven parameters are already documented in the schema, including the five required ones. The description contributes no additional parameter meaning, which is the expected baseline when the 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?

States a specific verb+resource ('Create a new compliance record') and clarifies scope with the parenthetical 'audit trail entry'. It stops short of distinguishing itself from close siblings like create_compliance_item or create_compliance_pm_schedule, which share almost identical naming.

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 only guidance offered is the required scope ('compliance_records:write'). There is no statement of when to use this versus create_compliance_item, create_compliance_pm_schedule, or bulk_create, nor any prerequisite about the referenced entities needing to exist first.

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