get_today_tasks

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

Annotations already declare this is a safe read (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the safety profile is covered. The description adds the semantic scoping rule (incomplete + due today or overdue), which is genuinely useful, but says nothing about result ordering, grouping by list, or whether completed-but-overdue tasks are excluded.

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 sentence with no filler, and the most consequential qualifier (due today or overdue) is placed where it is read first. Nothing to trim.

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 no-argument, read-only aggregation tool with no output schema, the description supplies the one thing that matters: which tasks are returned. Minor gaps remain around result shape (flat list vs grouped by list) and ordering, but nothing blocks correct invocation.

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 tool takes zero parameters and the schema is an empty object with full description coverage, so there is nothing for the description to disambiguate. Baseline 4 applies for a parameterless tool.

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?

States a specific verb (列出/List) and resource (tasks) narrowed by three concrete scope qualifiers: all lists, incomplete, due today or overdue. This is far more precise than a bare 'list tasks', though it never names how it differs from siblings like get_my_day, list_tasks, or search_tasks.

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 filter definition implicitly signals when the tool applies (a 'what's on my plate today' view), but there is no explicit when-to-use, no exclusions, and no pointer to the alternative tools that could also return tasks. Usage must be inferred.

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