manus_task_delete

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

Without annotations, the description carries the full burden. It discloses the destructive nature ('Permanently delete') and a restriction, but lacks details on side effects (e.g., impacts on related data), reversal possibilities, or permission requirements.

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 concise with two sentences, no filler, and front-loads the primary purpose. Every sentence adds value.

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?

While the tool is simple (1 required param, no output schema), the description fails to cover essential context for a deletion tool, such as whether the deletion is reversible, what happens to associated data, or whether confirmation is needed. Schema coverage is 0%, so the description should compensate but does not.

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 0% for the single parameter 'task_id', and the description adds no semantic meaning beyond the schema's type definition. It does not clarify format or origin of the ID, leaving the agent to guess.

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 action ('Permanently delete a task') and resource ('task'), and distinguishes which tasks cannot be deleted ('Agent-related tasks'), effectively differentiating it from sibling tools that perform other operations.

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 a clear exclusion condition ('Agent-related tasks cannot be deleted'), which aids in when-not-to-use. However, it does not explicitly mention when this tool should be used over alternatives or provide prerequisites like task state requirements.

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