Api applied controls create

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so safety is partly covered. The description adds nothing beyond that and is actively misleading by framing a create endpoint as something that can be 'viewed', with no mention of required auth, validation errors, or what a successful creation yields.

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?

It is a single short, front-loaded sentence with no padding, so it is concisely written — but the content is boilerplate that does little work, so brevity here is a byproduct of having nothing to say.

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 create mutation with an unconstrained free-form body, no output schema and no annotations explaining validation, the description leaves an agent unable to construct a valid call. Nothing about required fields, side effects, or the resulting resource is communicated.

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 single `body` parameter has 0% schema description coverage and is an untyped `anyOf` object with additionalProperties, so an agent has no idea what fields an applied control requires (name, status, category, owner, etc.). The description does not compensate in any way.

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 is generic Django-REST-Framework boilerplate ('allows applied controls to be viewed or edited') and never states that this endpoint creates a record, which only the tool name and title convey. Worse, 'viewed' points toward a read operation, blurring the distinction from siblings like applied_controls_list, _retrieve, _update and _partial_update.

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 on when to use this versus the many applied_controls siblings (list, retrieve, update, partial_update, duplicate, merge, batch_action). An agent has to infer 'create' purely from the tool name, with no stated preconditions.

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