Tasks Due This Week

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

With no annotations provided, the description carries the full burden. It discloses the 7-day window, which is useful behavioral detail, but omits edge cases like whether overdue tasks are excluded, whether completed tasks are included, and timezone handling. The description is minimal and does not address these potential ambiguities.

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 immediately conveys the tool's purpose. It is front-loaded and contains no fluff, earning a high score.

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 zero-parameter read tool with no output schema, the description is largely complete: it specifies the exact set of tasks returned. Minor gaps like sorting or project scope exist, but the low complexity and clear sibling set make the description sufficient.

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 schema coverage is 100% since there are no parameters to document. Baseline for 0 params is 4, and the description adds no unnecessary parameter details, which 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 'Get all tasks due within the next 7 days' clearly states the specific verb (get), resource (tasks), and scope (due within 7 days), effectively distinguishing it from sibling tools like ticktick_get_tasks_due_today, ticktick_get_tasks_due_tomorrow, and ticktick_get_overdue_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 description implies usage when needing tasks due this week, but does not explicitly mention when to prefer this over alternatives such as ticktick_get_tasks_due_in_days or ticktick_get_tasks_due_today. No exclusions or alternative guidance is provided, though the time range gives clear context.

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