Tasks Due Tomorrow

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

With no annotations, the description carries full responsibility for behavioral disclosure. It does not specify whether completed tasks are included, what constitutes 'due tomorrow' (e.g., timezone or tasks without specific times), or the format of the returned data. This is minimal for even a simple read tool.

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 sentence with no wasted words, achieving high conciseness and front-loading the core purpose.

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 tool's simplicity (zero parameters, no output schema), the description is adequate but leaves gaps. It doesn't explain the exact meaning of 'due tomorrow' (e.g., timezone handling, completed tasks) or why to pick this over get_tasks_due_in_days. For a basic list tool, it's usable 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?

The tool has zero parameters, so the baseline is 4. The description adds no parameter details but also doesn't need to, as the schema is empty.

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 that are due tomorrow" uses a specific verb (Get) and resource (tasks), with an explicit scope (due tomorrow). This clearly distinguishes it from sibling tools like get_tasks_due_today and get_tasks_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?

The description implies its use for retrieving tasks due tomorrow but does not explicitly state when to use it versus alternatives such as get_tasks_due_in_days or get_overdue_tasks. No exclusions or alternative recommendations are provided.

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