agenda

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

There are no annotations, so the description must disclose behavioral traits. It lists categories and implies retrieval of tasks but doesn't state whether it's read-only, how results are sorted/grouped, or any side effects. This lack of behavioral detail is a significant gap for an unannotated 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 extremely short and front-loaded, but it's a sentence fragment without a verb, which reduces clarity. It could benefit from a verb and more structured phrasing, though it has no wasted words.

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 existence of an output schema, return values are covered, but the description doesn't clarify the tool's core function or usage context. It also doesn't mention how categories are combined or whether tasks can appear in multiple categories, leaving gaps in completeness.

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 description explains the 'days' parameter via 'upcoming (next N days)', indicating that days controls the horizon for upcoming tasks. Since schema coverage is 0%, this compensation is valuable, though it doesn't explicitly name the parameter or mention its default.

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 lists categories (overdue, today, upcoming, in-progress/blocked) but lacks a verb or explicit resource, making it a noun phrase rather than a clear statement of what the tool does. It doesn't distinguish from sibling tools like list_tasks, which might also return task lists.

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 guidance is provided on when to use this tool versus alternatives such as list_tasks or search_tasks. There are no exclusions, alternatives, or contextual hints, leaving the agent to guess its appropriate use.

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