list_tasks

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

No annotations are provided, and the description lacks behavioral details such as pagination, ordering, default limit (100 is in schema but not mentioned), or error handling for invalid run_id. It simply says 'list tasks' without disclosing behavior beyond the basic function.

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 very concise (9 words) but under-specified. It is front-loaded but lacks necessary details that would make it useful for an AI agent. It earns its place but does not achieve conciseness with completeness.

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 4 parameters, no output schema, and a list operation, the description is incomplete. It fails to mention return format, pagination, ordering, or interaction with sibling tools. A more complete description would cover these aspects.

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 add meaning. It only says 'optional filters' without explaining what each filter does or providing context like allowed values or format. Parameter names (status, owner_agent, limit) are self-explanatory but the description adds no additional value.

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 'List tasks for a run with optional filters', specifying the verb (list), resource (tasks), scope (for a run), and filtering capability. It distinguishes from siblings like 'get_task' (single task) and 'get_ready_tasks' (specific status filter).

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 vs alternatives (e.g., get_ready_tasks, get_blocked_tasks). The phrase 'optional filters' is vague and does not help the agent decide between this and other filtered task listing tools.

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