List tasks

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

Annotations already provide the read-only, idempotent, non-destructive safety profile. The description adds a genuinely non-obvious behavioral detail: tasks without dates do not match a time-range query because of CalDAV filter semantics. This prevents a realistic and costly misunderstanding.

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?

Two sentences with no wasted words. The core purpose is front-loaded, and the second sentence earns its place by explaining an important edge case with a brief rationale.

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?

With a complete input schema, an output schema, and rich annotations, the description covers exactly the additional semantic context an agent needs. The date-filtering behavior and no-date exclusion are explained, while pagination, defaults, and formatting are already documented in the schema. Nothing essential is 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?

Schema coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by explaining that the time range applies to start or due dates, which the individual parameter descriptions do not state. It appropriately does not repeat the schema's per-parameter details.

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 defines a list operation over tasks, scoped to tasks with a start or due date inside a time range. This distinguishes it from list_events, list_journals, and the single-item get_task. It also states a clear exclusion: tasks with no date are never returned.

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 this is the tool for time-range queries over tasks, but it does not explicitly state when to use it versus sibling tools such as get_task or list_events. No alternatives or when-not-to-use guidance is provided. The intended usage is inferable but not spelled out.

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