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

No annotations are provided, so the description carries the full behavioral burden. It does disclose that deletion is not the default and should only occur on explicit user request, which is useful. However, it does not state that deletion is irreversible/permanent or describe any side effects beyond the name.

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?

Two short sentences with no filler. The core action comes first, and the important usage caveat follows immediately. Every word earns its place.

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?

The tool is simple, but with no output schema, no annotations, and low parameter coverage, the description leaves gaps. It gives good usage guidance but does not explain how to obtain listId/taskId or what happens after deletion. It is minimally adequate but not complete.

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 only 33%; only mailbox is documented. The description adds nothing about listId or taskId, and those parameters are undocumented in the schema. Since coverage is low, the description should have compensated, but it does not.

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 states a specific verb and resource: 'Delete a task.' It also explicitly distinguishes deletion from completion, which is the key sibling distinction given complete_google_task exists. An agent can immediately tell this tool's purpose from the title and first sentence.

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?

The description gives explicit guidance: 'Completing it is almost always what the user means — only delete when they say delete.' This directly tells the agent when to avoid this tool and prefer completion, which is a clear alternative-usage condition even though complete_google_task is not named.

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