list_tasksRetrieve recent background tasks from AgentHub, newest first, and filter by status or limit to monitor delegated coding jobs.
Recent background tasks, newest first.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| status | No |
Changes observed during successful MCP inspections.
v1.2.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds ordering (newest first) and a recency bias, but omits the default limit, the 500 cap behavior, and whether results are truncated or paginated.
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 short sentence with the ordering constraint front-loaded and no wasted words. It is efficient, though its brevity is partly the source of the missing detail rather than a virtue in itself.
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?
With 0% schema coverage, an enum parameter, and no output schema, the description should explain filtering by status and the meaning of limit. It does neither, leaving the tool under-specified for a filterable list operation.
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% for two parameters: limit and status. The description never mentions either, so an agent gets no guidance on the status enum values or on how limit interacts with 'recent' results. It fails to compensate for the coverage gap.
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?
States the resource (background tasks) and an ordering guarantee (newest first), but the action verb is only implied by the name and there is no differentiation from siblings like get_task, wait_task, or list_agents. An agent can tell it lists something recent, but the exact scope is vague.
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 indication of when to use this versus get_task, wait_task, or list_agents. There is no mention of whether this is a global list or session-scoped, nor any prerequisite or exclusion guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.