Api entity assessments create

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

With readOnlyHint=false and destructiveHint=false already declared, the description adds nothing: no note that a payload is written, no required-field expectations, no side effects, no mention that openWorldHint=true implies external-facing impact. The "viewed" wording also blurs the read/write distinction the annotations set.

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 short, but the single sentence is boilerplate that does not earn its place — it consumes the entire description budget without conveying the operation, payload shape, or any constraint.

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?

A write tool with no output schema, no documented parameters, and only default annotations. Everything an agent needs (what to send, what is created, what identifies an entity assessment) is missing, so the description is inadequate for the tool's complexity.

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?

There is a single untyped `body` parameter with additionalProperties=true and 0% schema description coverage. The description says nothing about what belongs in the body or which fields the API expects, so an agent has no way to construct a valid call from this definition.

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 DRF-generated boilerplate: "API endpoint that allows entity assessments to be viewed or edited." It names the resource but never states the actual operation (create) despite the tool name ending in _create, and it does not distinguish this tool from siblings like entity_assessments_retrieve, _list, or _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 when-to-use guidance and no mention of alternatives. Worse, "viewed or edited" actively points an agent toward read semantics, which could cause it to call this create endpoint when it meant entity_assessments_retrieve.

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