Api task templates destroy

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

Annotations declare destructiveHint=true and readOnlyHint=false, but the description frames the tool as an export/read capability. This directly contradicts the safety profile an agent needs, and gives no information about irreversibility or prerequisites for deletion.

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?

The text is short, but brevity here is not conciseness — it is a single irrelevant sentence that conveys no actionable information for the tool's actual behavior.

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 destructive, open-world, non-idempotent-in-effect deletion tool with no output schema and an undocumented parameter, the description provides none of the context needed to invoke it safely or correctly.

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?

There is one required parameter (id) with 0% schema description coverage, and the description says nothing about it. With low coverage the description is expected to compensate, and it does not mention the identifier at all.

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 says "Generic export mixin for CSV/XLSX exports," which describes an export capability, not a deletion of a task template. The tool name and title indicate a destroy operation, so the description actively misleads about what the tool does.

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 tool versus alternatives (e.g., partial_update, batch_action_create, or other destroy siblings). The stated use case (CSV/XLSX export) points to entirely different sibling tools such as task_templates_export_csv_retrieve.

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