Api task templates create

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

Annotations declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, i.e. a non-idempotent write. The description instead frames the tool as an export (a read-like operation), contradicting the mutation semantics an agent needs to know about. Nothing is said about payload expectations, side effects, or required permissions.

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 and front-loaded, so it does not waste tokens, but the single sentence conveys no usable information about this tool. Brevity here is under-specification rather than 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 create tool with a free-form body, no output schema, and no documented parameters requires the description to explain the payload shape and mutation semantics. It does none of that, so an agent cannot call it correctly from this definition.

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% and the sole 'body' parameter is an untyped free-form object with additionalProperties true. The description offers no information about what fields the body should contain, leaving the agent with no way to construct a valid request.

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 neither a create operation nor task templates. It appears to be a copy-pasted framework docstring and actively misleads an agent 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?

There is no when-to-use guidance, no mention of the sibling list/update/retrieve tools for task templates, and no exclusion conditions. The one sentence describes an unrelated export concern rather than the create workflow.

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