Api risk scenarios qualifications count retrieve

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

The description says the resource 'can be viewed or edited' while annotations declare readOnlyHint=true and destructiveHint=false. That is a direct contradiction about whether this endpoint mutates state, and it adds nothing else (no mention of counts, aggregation scope, or empty result behavior).

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 sentence with no filler, so it is technically concise. But brevity here comes from being generic boilerplate rather than from front-loading useful information, and the one clause it contains is misleading.

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?

With no output schema and no annotations covering the return payload, the description is the only place an agent could learn that this returns a qualification count rather than a list or object — and it says nothing of the sort. Completely inadequate for the tool's actual purpose.

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 input schema has zero parameters, so there is no parameter semantics for the description to explain; the baseline of 4 applies. The description neither helps nor harms in that dimension.

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 stock Django REST Framework boilerplate ('allows risk scenarios to be viewed or edited') and never mentions what this endpoint actually is: a count of risk scenario qualifications. It names the resource but not the specific operation, so an agent has to fall back entirely on the title/name to guess the tool returns a count.

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 exclusion of alternatives, and no hint that this is a read-only aggregation rather than a detail fetch. The many siblings (risk_scenarios_list, count_per_level_retrieve, etc.) are never referenced, so selection between them is left entirely to name guessing.

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