todo_list

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

With no annotations, the description carries the burden of disclosing behavior. It mentions the sort order and filter capabilities, which adds some context, but it does not explicitly state that this is a read-only operation, describe pagination behavior, or mention any side effects. The word '查询' implies query, but not fully explicit.

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 a single, concise sentence that leads with the main purpose and follows with key behaviors. Every phrase adds value with no unnecessary words, making it appropriately sized and front-loaded.

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 tool has six optional parameters and an output schema, so return values are likely covered elsewhere. However, the description omits details about pagination (limit/offset), how filters behave (exact vs. partial match), and any potential side effects. It is acceptable for a simple list tool but not fully complete.

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%, so the description must compensate. It clarifies the meaning of four parameters (status, category, keyword, tag) as combinable filters, but it does not explain limit and offset, which are also parameters. Partial compensation but not complete for all six parameters.

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 queries a todo item list (查询事项列表) and specifies supported filters (status/category/keyword/tag) plus sort order (creation time descending). This distinguishes it from sibling tools like todo_get which retrieves a single item, and time_list which queries time logs.

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 implies usage for listing todos with combined filters, but it does not explicitly mention alternatives or when not to use this tool. For example, it does not direct users to todo_get for single-item retrieval or note any exclusions, so the guidance is only implied.

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