list_upcoming

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

The description discloses the filtering and ordering behavior, which is good given no annotations. However, it fails to explicitly state that the operation is read-only or describe any side effects or limitations (e.g., pagination behavior).

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 concise with two clear sentences. No fluff or redundant information. The definition is front-loaded.

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?

The tool is simple and there is an output schema, so return format is covered. However, the description lacks details about pagination (defaults, maximums) and does not explain the parameters. With many sibling tools, additional context could help differentiation.

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 input schema has two parameters (limit, offset) with 0% description coverage in the schema itself. The description does not mention or explain these parameters, forcing the agent to rely solely on parameter names. This is insufficient.

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 'List tasks scheduled for a future date' and defines the criteria (start date after today, not completed, not trashed, ordered by start date then deadline). This distinguishes it from sibling list tools like list_today or list_anytime.

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 provides clear criteria for when to use this tool (future start dates), but does not explicitly tell the agent when not to use it or mention alternatives. However, the criteria implicitly guide usage.

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