list_open_tasks

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

There are no annotations, so the description must carry behavioral disclosure. It adds useful behavior: tasks are open, sorting is newest first, and category is optional with open-ended examples. However, it does not state read-only guarantees, pagination/truncation behavior, or effects of the limit parameter.

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 one efficient sentence with the core action and ordering front-loaded, followed by the optional category context. Every phrase adds value and there is no wasted wording.

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?

Given an output schema exists, return values do not need describing. The description covers the core list behavior and category filter, but it omits limit semantics and any guidance about when to choose this tool over search_tasks. For a simple tool this is adequate, but not fully complete.

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%, so the description must compensate for parameter meaning. It adds examples for category ('grocery, bills, people, inbox, …') and says it is optional, but the limit parameter is entirely undocumentted in the description. With two parameters, only half gain real semantic explanation beyond the schema.

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 specifies the verb 'List', the resource 'open tasks', and provides ordering ('newest first') plus an optional category filter with examples. It does not explicitly distinguish itself from the sibling tool search_tasks, so it meets the clarity bar without fully differentiating from alternatives.

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 list_open_tasks versus search_tasks or other sibling tools. The category examples hint at filtering use, but there are no explicit when-to-use, when-not-to-use, or alternative-routing statements.

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