Api task templates list

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

Annotations already declare readOnlyHint/idempotentHint/openWorldHint, so safety is covered, but the description adds no operative context — not pagination behavior, not what the 'optimized data' means for the returned payload, not whether filters are combinable. Worse, it spends its only sentence on server internals that give the agent no actionable signal.

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 devoted to an implementation note rather than a front-loaded purpose statement, so its brevity does not earn its place.

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 list tool with 17 undocumented optional parameters, no output schema, and no annotations explaining return shape, the description supplies nothing an agent needs in order to call it correctly — no filter semantics, no pagination model despite limit/offset/max_pages existing.

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 17 parameters (id, name, folder, search, ordering, is_recurrent, last_occurrence_status, max_pages, etc.), and the description adds zero meaning for any of them. The agent has no idea what values these filters accept or how they interact.

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 describes an internal Django implementation detail ('Override the list method to inject optimized data into the serializer context') rather than telling an agent what the tool does. Only the tool name and title hint that it lists task templates; the description itself never states the verb+resource that an agent needs.

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 such as ciso_assistant_api_task_templates_retrieve or _object_retrieve, and no conditions that would select this tool over its siblings.

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