List Zero Tasks

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds useful context beyond annotations by scoping results to the signed-in user's tasks, indicating that q searches title and description, and that before/after narrow the result by time.

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?

A single, tightly written sentence that front-loads the action and resource, then states search scope and optional time filtering. No filler or repetition.

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 read-only list/search tool with strong annotations and optional parameters, the description plus schema cover the core invocation details: what is searched, user scope, and time boundaries. It could mention return format or alternative use of search_zero, but these are not blocking for correct basic use.

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 describes after and before as time boundaries but leaves q and limit undocumented. The description partly compensates by explaining that search is by title and description and that time windowing is optional, but it does not clarify limit behavior or the exact default semantics of q.

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 identifies a specific verb and resource: listing or searching the signed-in user's Zero tasks, with optional time narrowing. This clearly distinguishes it from create/update/get_task, though it does not explicitly contrast it with the sibling search_zero.

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 when to use the tool: when you need to list or search the signed-in user's tasks by title/description or within a time window. It provides no explicit guidance about when to prefer search_zero or other search alternatives, so the routing is left to inference.

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