wealthbox.tasks.delete

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

With no annotations, the description must disclose behavioral traits but only states the obvious. It does not reveal whether deletion is permanent, what side effects occur, or if authorization is required, making it inadequate for a destructive 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 (two words), but it is under-specified rather than concise. It omits critical information and reads as a tautology of the tool name, failing to earn 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?

For a low-complexity tool with one parameter and no output schema, the description still proves incomplete. It lacks any context about the deletion behavior, expected id format, or what happens to associated data, making it insufficient for reliable invocation.

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 a single 'id' parameter with 0% description coverage, and the description does not compensate by explaining that id refers to the task ID. The word 'Delete task' adds no meaning beyond the schema, leaving the parameter's context implicit.

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 'Delete task' uses a specific verb (delete) and resource (task), clearly indicating the tool's purpose. It differentiates from sibling tools like tasks.list or tasks.update, though it doesn't explicitly distinguish from other resource-specific delete tools.

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 provides no guidance on when to use this tool versus alternatives (e.g., tasks.update for modifications). No prerequisites, idempotency, or context are mentioned, leaving the agent without decision-making information.

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