workiva_delete_task

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It only says 'Delete a task' without mentioning whether deletion is permanent, any permission requirements, side effects, or what happens to associated data. This is a significant transparency gap for a deletion operation.

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 description is extremely short, which is not conciseness but rather under-specification. It consists of one sentence and an args list, providing no meaningful structure beyond what the schema already offers.

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?

Although the tool has a simple single-parameter signature and an output schema, the description lacks essential context about the deletion's impact, reversibility, or any special cases. The minimal text leaves the agent without enough information to safely invoke the tool.

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?

The schema has 0% description coverage, and the description attempts to compensate by noting that task_id is 'The task UUID.' This adds a minimal detail about the expected format, but it mostly restates the parameter name and schema type (string). It does not explain how to obtain the task_id or any constraints.

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 clearly states 'Delete a task' with a specific verb and resource. It is unambiguous and distinct from siblings like create_task or update_task, though it does not elaborate on any task-specific scope or context.

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 is provided on when to use this tool versus alternatives, such as Workiva_update_task or Workiva_submit_task. The description simply states the action with no context or exclusions.

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