Api policies priority retrieve

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

Annotations declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, yet the description claims the endpoint allows records to be 'edited' — a write capability the tool cannot perform (no parameters at all). This directly conflicts with the structured safety metadata and also misidentifies the affected resource, providing zero usable behavioral context.

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, so it is not bloated, but the one sentence it spends is boilerplate that carries no information about this specific endpoint. Brevity without content does not earn credit.

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 parameters, the description is the only place a caller could learn what a 'priority retrieve' returns (presumably the priority enum/choice list) and how it differs from the priority chart-data sibling. It supplies none of that, leaving the agent to guess at the response shape and intended use.

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 no parameters, so there is nothing for the description to explain beyond the schema; the baseline for zero-param tools applies. The description neither helps nor harms here, though its mention of editing implies inputs that do not exist.

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 sentence is generic DRF-viewsets boilerplate: it says the endpoint 'allows applied controls to be viewed or edited', which describes a different resource ('applied controls') than the tool's own name ('policies priority'). The actual purpose — returning the priority choice/enum values used by policies — is never stated, so an agent cannot distinguish it from siblings like policies_priority_chart_data_retrieve or policies_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 mention of when not to use it, and no reference to any of the many sibling endpoints (policies_priority_chart_data_retrieve, policies_per_status_retrieve, policies_retrieve). The agent must infer the selection rule entirely from the tool name.

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