Api task nodes list

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds only an implementation note about serializer context, saying nothing about pagination, filtering behavior, ordering defaults, or what 'optimized data' means for the returned records.

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 there is no verbosity problem, but the one sentence is spent on internal framework detail rather than on the information the caller needs. Brevity here is under-specification dressed as conciseness.

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?

A 16-parameter, zero-required list endpoint with no output schema and no useful description is essentially undocumented. Nothing tells an agent how to paginate, what the due_date operator suffixes do, or what 'past' and 'task_template' filter on.

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?

Schema description coverage is 0% across 16 parameters (id, past, limit, offset, search, status, due_date, ordering, max_pages, task_template, and the due_date__gt/lt/gte/lte/year/month variants), and the description documents none of them. It neither explains the filter semantics nor the pagination/ordering contract an agent needs.

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 text reads as an internal Django docstring ('Override the list method...') rather than a statement of what the tool does for a caller. It never says it lists task nodes or what a task node is, so an agent must infer purpose entirely from 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?

No when-to-use, no when-not-to-use, and no reference to alternatives such as ciso_assistant_api_task_nodes_retrieve, task_nodes_object_retrieve, or task_nodes_evidences_list. The 'inject optimized data into serializer context' phrasing gives no selection criteria.

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