Api policies list

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The only added signal is 'inject optimized data', which vaguely hints at enriched payloads but discloses nothing concrete about pagination, filtering behavior or result shape.

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 short, but the single sentence is internal implementation jargon that does not front-load the tool's purpose. Brevity here reflects under-specification rather than efficiency; the one sentence does not earn its place for a caller.

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 45-parameter list endpoint with no output schema and no parameter descriptions, the description supplies essentially nothing an agent needs: no object being listed, no filterable fields, no pagination contract, no return shape.

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?

45 parameters with 0% schema description coverage and no types on most (all anyOf with no definitions), and the description says nothing about any of them. Filtering, ordering, search, offset/limit, max_pages and id are entirely undocumented, leaving an agent unable to construct a correct call.

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 a Django developer docstring ('Override the list method to inject optimized data into the serializer context') rather than a statement of what the tool does for a caller. An agent can infer it is a list endpoint for policies only from the tool name, not from the description, which never mentions policies or listing semantics.

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?

No guidance on when to use this versus the many sibling policy endpoints (policies_retrieve, policies_object_retrieve, policies_autocomplete_retrieve, policies_ids_retrieve, policies_analytics_retrieve). The sentence gives a caller no selection criteria at all.

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