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

The description discloses critical behavioral details beyond the annotations: only TODO instances are removed, in-progress/completed ones remain as history, the returned removed field indicates how many instances were removed, the operation is irreversible, and the agent must confirm with the user before executing. This fully complements destructiveHint=true and openWorldHint=true.

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 organized into scannable sections (何时用, 组合链, 口径/坑) with every sentence delivering actionable information. It is dense without being verbose, and the most important usage guidance appears first.

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?

Despite having no output schema and only one parameter, the description covers the trigger, prerequisite chain, alternatives, exact effects, irreversibility, confirmation step, and return field. Nothing essential is missing for an agent to decide when and how to call this destructive tool correctly.

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%, but the description compensates by explaining how to obtain seriesId via get_collaboration_goal(include:['series']) and by referencing series.openCount for pre-confirmation. It does not explicitly define 'seriesId' as the recurring-rule identifier, but the chain instruction makes the parameter's origin and role clear.

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 the precise trigger ('用户说「这件周期性的事不用再做了」') and specifies the resource (periodic task rule) and the action (remove TODO instances). It also distinguishes itself from update_task_series by naming the sibling and the exact condition under which that sibling should be used instead.

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 '【何时用】' section gives a clear user-intent trigger, and the '【组合链】' section prescribes the exact upstream call (get_collaboration_goal with include:['series']) to obtain seriesId. It explicitly names update_task_series(active:false) as the alternative for rescheduling/pausing, with a warning not to use this tool for that case.

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