list_tasks

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

The description reveals that the tool lists both running and recently completed tasks and that they are stored in 'agent pool memory'. However, it does not explain what qualifies as 'recently completed' or whether repeated calls yield consistent results. Without annotations, more detail about idempotency or caching would improve transparency.

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 a single clear sentence with 12 words, no redundancy. It efficiently conveys the core functionality.

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 no output schema, the description should clarify what data is returned for each task. It lacks details like fields, pagination, or limits. The phrase 'recently completed' is vague. Overall adequate but could be more 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?

There are no parameters in the schema, so parameter information is not needed. The description does not add parameter-specific meaning, but with zero parameters the baseline is 4.

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 states the verb 'list', the resource 'background tasks', and the scope 'currently running or recently completed in the agent pool memory'. It distinguishes itself from sibling tools like 'cancel_task' and 'list_pipelines' by specifying background tasks and memory scope.

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 on when to use this tool versus alternatives such as 'get_pipeline_status' or 'list_sessions'. No mention of when not to use or side effects.

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