gws.tasks.delete

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

The description discloses irreversible destructive behavior ('cannot be undone', 'Permanently delete') and requires confirmation, adding context beyond the annotations (destructiveHint=true). It also mentions the return value (deleted task's ID and list), which is not present in any structured field.

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?

Three sentences, front-loaded with the core action and critical detail (irreversibility). Every sentence provides value: purpose, user guidance, alternative, default, and return value. No fluff.

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 simple delete tool with three parameters and no output schema, the description is comprehensive. It covers behavior, caution, alternative tool, default parameter value, and return value, making it fully adequate for an agent to use 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?

Schema covers all parameters (100% coverage), but the description reinforces the tasklist default ('@default') and clarifies that tasklist defaults to the account's default list. This adds practical meaning beyond the schema's parameter descriptions.

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 the tool's purpose: 'Permanently delete a task from a task list.' It uses a specific verb and resource, and distinguishes itself from the sibling tool tasks.complete by explicitly contrasting deletion with marking done.

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 explicit usage guidance: 'To mark a task done without removing it, use tasks.complete instead.' Also instructs to confirm with the user before calling due to irreversibility, and notes the default tasklist behavior.

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