Api compliance assessments map from create

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

Annotations already indicate this is a non-readOnly, non-destructive, non-idempotent, open-world mutation. The description adds only that data is mapped from a source audit into the current one, without explaining what data is copied, whether existing data is overwritten, or what permissions/preconditions are required.

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 a single efficient sentence with no wasted text. However, "this one" is an unclear antecedent that reduces precision.

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 mutation tool with an ambiguous single parameter and no output schema, the description should explain the mapping operation, prerequisites, and effect on existing data. It provides only a high-level sentence that leaves core behavior unspecified.

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 coverage is 0%, and the sole parameter is just `id` with no description. The prose mentions a "source audit" but does not clarify whether `id` identifies the source audit, the target assessment, or some other object.

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 a specific action, mapping data from a source audit into "this one," but it does not identify the resource as a compliance assessment and leaves the target ambiguous. It also does not distinguish this tool from the sibling map-from-preview retrieval tool.

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?

There is no guidance about when to use this tool, when not to use it, or whether a preview step should happen first. The agent is left to infer usage from the name alone.

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