get_tasks

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

The description discloses key behavior: when listId is omitted, all VTODO-capable lists are queried and results are tagged with source list. Being a retrieval operation, no side effects are expected, and the description adds value beyond the schema's parameter descriptions.

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?

Three short sentences, each adding information: purpose, listId omission behavior, and prerequisite. No redundant phrasing.

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?

For a straightforward read operation with three well-documented parameters, the description covers the essential behavior and output tagging. It lacks detailed return structure but that is not critical given the simple tool and no output schema.

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 schema already fully describes limit, listId, and status (100% coverage). The description elaborates on the listId parameter by mentioning all VTODO-capable lists and result tagging, which goes beyond the schema's note to query all lists.

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?

Clearly states it retrieves tasks from Nextcloud, distinguishing from calendar/notes/files siblings. The scope of querying all lists when listId is omitted is specified, and the prerequisite relationship with get_task_lists is noted.

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?

Provides guidance to call get_task_lists first to discover list IDs, which helps with parameter selection. Does not explicitly contrast with create/update tools, but the read-only nature is implicit and the sibling names suffice.

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