Api entity assessments metrics retrieve

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

The annotations declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, but the description asserts the endpoint allows entity assessments to be "viewed or edited" — explicitly claiming write capability that the annotation denies. Beyond the contradiction there is no behavioral context added: no indication of what metric shape, aggregation or time frame is returned.

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?

A single short sentence with no padding, so it is structurally fine and front-loaded. But it is boilerplate rather than substance — it is concise because it says almost nothing, not because it was edited down.

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 zero-argument read tool with no output schema, the description is the only place an agent can learn what comes back, and it says nothing about the metrics payload. Combined with the misleading "edited" wording, the agent lacks the information needed to call this correctly rather than accidentally reaching for a sibling.

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 tool takes zero parameters and the schema is an empty object, so there is nothing for the description to clarify. Baseline 4 applies; the description neither helps nor harms parameter understanding.

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?

"API endpoint that allows entity assessments to be viewed or edited" restates the resource name and the generic Django-REST-Framework boilerplate, and never says what makes this endpoint distinct: it is a metrics endpoint. An agent cannot tell from this text whether it returns metrics, a detail record, or a writable form, nor how it differs from siblings such as entity_assessments_retrieve or entity_assessments_status_retrieve.

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, no stated preconditions, and no mention of any alternative. With roughly ten sibling entity_assessments_* tools (list, retrieve, status_retrieve, conclusion_retrieve, cascade_info_retrieve) the agent must guess which one to select; nothing in the description routes it.

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