task_list

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

The description starts with '[READ]' indicating it's a read-only operation, and explains the return format including the truncated field. No annotations exist, so the description carries the burden and does well, though it omits details like error handling.

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 concise and well-structured: first line states purpose, second line shows return format, third line explains truncated, then Args section. No wasted words.

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 the lack of annotations and output schema, the description covers the return format, parameter meanings, and usage of the truncated field. It could be more complete with error scenarios or prerequisites, but it is sufficient for 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?

All three parameters (status, limit, target) are explained in the description with specific allowed values for status and default values for limit and target. This adds significant value beyond the schema which has no descriptions.

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 it lists XO tasks with optional filtering by status. The verb 'list' and resource 'XO tasks' are specific and distinct from sibling tools that list other resources like VMs or hosts.

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?

Guidance on optional filtering by status and handling truncated results is provided. However, there is no explicit when-to-use or when-not-to-use compared to other tools, though the tool name makes its purpose clear.

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