delete_fs_tasks_id

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

No annotations provided, so description carries full burden. It discloses key behaviors: stops task if running, no rollback, and lists possible error codes. This is good transparency for a delete tool, though some details (e.g., concurrency) could be added.

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?

Description is two sentences plus an error code list. Front-loaded with main action. The error code list is lengthy but potentially useful. No wasted words.

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?

Given an output schema exists (context signals), return values need not be described. Description covers the deletion action, side effects, and error codes, providing a complete picture for a simple delete operation.

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 coverage is 0% (no description in schema), but tool has only one parameter 'id', which is self-explanatory. Description does not add extra meaning beyond the schema, but the simplicity of the parameter mitigates the gap. Adequate.

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 'Deletes the FsTask task with the given id', specifying the action (delete) and resource (FsTask). It also mentions stopping if running, adding specificity. Distinguishes from siblings as it targets a unique resource.

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?

Provides consequence information ('No rollback is done, if a file as already been processed it will be left as is') but no explicit guidance on when to use this tool vs alternatives. Usage is intuitive for a delete action, but lacks comparative context.

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