tasks

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

Mentions 'Refreshes liveness and resolves spawned_cid lazily', disclosing side effects and lazy resolution behavior. No annotations provided, so description carries this burden effectively.

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?

Two concise sentences: first clearly lists output fields, second adds behavioral nuance. No fluff, every sentence earns its place.

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?

Output schema (present but not shown) likely describes return values, so description focuses on listing and behavior. However, it omits parameter semantics and could elaborate on 'lazily' or pagination, leaving some gaps.

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 has two parameters (include_ended, k) with 0% description coverage. The description does not mention or explain any parameters, failing to add meaning beyond the schema's basic type/default info.

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?

Starts with 'List spawned tasks' providing a clear verb and resource. Lists specific fields included (id, pid, status, etc.), distinguishing it from sibling tools like 'task_logs' and 'spawn_status'.

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 like 'spawn_status' or 'task_logs'. No context for when not to use or prerequisites.

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