Tasks Due in N Days

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the basic read operation and does not clarify whether the date range includes today, whether overdue tasks are excluded, whether completed tasks are included, or how results are ordered. The meaning of 'due' is left ambiguous.

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, direct sentence that is front-loaded and free of fluff. It is appropriately sized for a simple tool, though some behavioral details could have been added without sacrificing conciseness.

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?

Given the simplicity of the tool (one parameter, no output schema), the description is minimally adequate. However, the presence of many sibling tools with similar date-based filters means the description lacks enough context to help the agent decide when this tool is the right choice. It does not mention return format, filtering semantics, or relationship to other tools.

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 for the single parameter 'days' is 100%, with the schema already providing a clear example. The description only reiterates the concept and adds no additional semantics or format details beyond the schema.

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 N days' clearly identifies the verb (get), resource (tasks), and scope (due within N days). The customizable N distinguishes this from sibling tools like 'due today' or 'due this week'.

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?

No usage guidance is provided. The description does not explain when to use this tool instead of alternatives such as ticktick_get_tasks_due_today, ticktick_get_tasks_due_this_week, or ticktick_get_overdue_tasks. There is no mention of exclusions or prerequisites.

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