Api policies todo retrieve

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

Annotations declare readOnlyHint=true and idempotentHint=true, but the description says the endpoint allows items to be 'viewed or edited', implying write capability. That contradicts the read-only annotation, and no other behavioral context (scope, filtering, return shape) is added.

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, so it is structurally efficient. But the sentence is generic boilerplate that does not earn its place because it misdescribes the resource and the operation.

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 parameter schema, the description carries the full burden of explaining the 'todo' semantics and the return set, and it does neither. An agent cannot infer what this endpoint returns or why it exists.

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 closed, so there is nothing for the description to disambiguate. Baseline 4 applies.

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 DRF boilerplate ('API endpoint that allows applied controls to be viewed or edited') and never explains what the 'todo' collection is. Worse, it names 'applied controls' as the resource while the tool is scoped to policies, so the stated resource conflicts with the tool name.

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 indication of when to call this versus the many siblings like ciso_assistant_api_policies_to_review_retrieve or ciso_assistant_api_applied_controls_todo_retrieve. The agent gets no routing guidance at all.

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