remove_task

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

No annotations are provided, so the description carries full burden. It discloses the deletion action and the return format (success, task_id, message or error), and mentions the user role restriction. However, it does not describe potential side effects (e.g., cascading deletions) or irreversibility, leaving some ambiguity.

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 concise, front-loaded with the core action, then provides permission info and a structured argument/return list. It mixes Japanese and English but remains clear. A minor deduction for not fully explaining the contradiction.

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 deletion tool, the description covers the essential: what it does, who can use it, parameters, and return format. An output schema exists (though not shown), which complements the description. It could elaborate on post-deletion effects, but overall it is adequate.

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%, so the description must compensate. It adds meaning by labeling parameters in Japanese. However, there is a contradiction: the description marks 'caller_agent_id' as required, but the input schema lists it as optional with a default of null. This misleads the agent.

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 'タスクを削除する' (Delete a task), using a specific verb and resource. Among sibling tools, it uniquely identifies the deletion action, distinguishing it from create, reopen, update, etc.

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 includes a permission note 'Owner と Admin のみ使用可能' (Only Owner and Admin can use), providing a clear usage constraint. However, it does not explicitly state when to use this tool versus alternatives or mention when not to use it.

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