upcoming_tasks

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

No annotations are provided, so the description must carry the full burden. It mentions auth and multi-value filter behavior, but fails to disclose other behavioral aspects such as read-only nature, pagination, rate limits, or sorting, leaving significant gaps.

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 extremely concise: three sentences plus tags, with no wasted words. The purpose is front-loaded, and the structure is clean and efficient.

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 11 parameters, no output schema, and no annotations, the description is far from complete. It does not define 'active tasks', how filters combine, the meaning of 'local upcoming window', or the limit parameter, leaving critical context missing.

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?

With 0% schema description coverage, the description must compensate but only adds a general statement about multi-value filters. None of the 11 parameters (e.g., local_date, days, project_ids) are explained, leaving the agent without necessary semantic context.

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 returns active tasks due within a local upcoming window, distinguishing it from siblings like overdue_tasks. It uses a specific verb+resource and mentions the scope, making the purpose unambiguous.

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 notes auth requirements and that multi-value filters accept list or single string, but lacks explicit guidance on when to use this tool versus alternatives like query_tasks. The related tools list hints but does not provide clear when-not or exclusion criteria.

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