list_tasks

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

With no annotations provided, the description carries the full behavioral burden, but it only says where tasks are stored. It does not disclose what the tool returns, whether completed tasks are included, ordering, read-only nature, or any other runtime 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 short and concise, but it is under-specified rather than usefully concise. It does not state the action or behavior the tool performs, so the single sentence does not earn its place.

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 data-model context (VTODO on the calendar) is useful, but it is far from complete. There is no output schema, no annotation, no param semantics, and no differentiation from sibling tools, leaving an agent with critical gaps for invoking this tool correctly.

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 description coverage is 0%, and the description provides no parameter semantics. 'calendar', 'timezone', and 'include_done' are left entirely unexplained, so an agent cannot determine valid values or side effects.

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 'Reminders and tasks stored as VTODO on the calendar' describes a data model, not an action. It does not explicitly say the tool lists tasks, so an agent must infer the verb from the tool name. It adds some resource context but is closer to a tautology than a clear purpose statement.

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 given about when to use this tool versus alternatives such as list_events or create_task. The mention of VTODO and calendar suggests a relationship to calendar data, but there are no explicit usage conditions or exclusions.

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