Api policies to review retrieve

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

The description says the endpoint allows records to be 'viewed or edited', but annotations declare readOnlyHint=true and destructiveHint=false. A retrieve tool that claims to allow editing directly contradicts the structured safety profile, and no other behavioral context (scope of 'to review', pagination, auth) is provided.

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 padding, but the space it occupies is spent on boilerplate about a different resource rather than on the tool's actual scope. Brevity here reflects an empty payload, not efficient communication.

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-parameter retrieval endpoint with no output schema and no annotations about return shape, the description should at least say what collection is returned and what 'to review' filters on. Instead it describes an unrelated entity, leaving the agent with no idea what comes back.

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, so there is nothing for the description to disambiguate and the baseline of 4 applies. No parameter-related omissions are possible here.

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 name and title indicate a retrieval of policies that need review, but the description talks about a completely different resource ('applied controls'). It is generic DRF boilerplate that does not state what this endpoint returns, so an agent cannot tell its purpose from the description itself.

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 alternatives, and no explanation of what 'to review' means (which status/due condition triggers inclusion). An agent sees dozens of sibling 'to_review' and 'policies_*' tools with nothing to discriminate among them.

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