タスクリスト削除

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

Annotations already declare destructiveHint=true, and the description adds critical behavioral context: cascading deletion of all tasks and irreversibility ('取り消せない'). This goes beyond the annotation and is essential for an agent to assess the safety of the 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?

Two short, high-value sentences. The primary action and its most important side effects are front-loaded. No filler or redundancy.

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 operation with a single parameter, all necessary context is provided: what is deleted, what else is deleted, and irreversibility. The destructive annotation and schema fully cover the remaining needs. No missing information.

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 input schema covers 100% of parameter descriptions ('削除するタスクリストの ID'), so the tool description adds no additional meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 clear verb ('削除する' = delete) and resource ('タスクリスト' = tasklist), and explicitly notes that all contained tasks are also deleted, distinguishing it from sibling delete-task. The purpose is unmistakable.

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?

While it doesn't explicitly name alternative tools, it clearly warns that all tasks within the tasklist are deleted and that the action cannot be undone. This implicitly tells an agent not to use this tool if they only want to delete a single task or if they need to preserve tasks, providing effective usage context.

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