todo_create_preview

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

Discloses key behavioral trait: dry-run and no database write ('不写库'), which is essential since no annotations are provided. However, it does not elaborate on what the 'impact list' contains or any validation behavior, leaving some gaps.

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?

A single concise sentence that front-loads the purpose, includes the dry-run note, and gives the follow-up call—no unnecessary words.

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?

The description covers the core workflow and non-destructive nature, but with 7 parameters and no schema descriptions, it leaves parameter semantics entirely unexplained. The existence of an output schema mitigates return-value documentation, yet the overall context is incomplete for a new user.

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%, and the description provides no information about parameters such as title, category, due, tags, notes, metadata, or priority. It neither explains required fields nor value constraints, failing to compensate for the schema's lack of descriptions.

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 uses the verb '预览' (preview) with a clear resource ('创建事项的影响' - impact of creating a todo), explicitly distinguishes from the sibling 'todo_create_apply' which executes, and establishes the preview/apply workflow.

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?

Explicitly instructs to call this tool first to display the impact list, then call 'todo_create_apply' to execute, providing clear when-to-use guidance and direction to the companion tool.

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