a2a_list_tasks

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

With no annotations, the description carries the burden of disclosing behavioral traits. It mentions pagination but does not clarify that this is a read-only operation, how results are ordered, whether it reads tasks 'from' or 'to' the agent (the role parameter), or what happens when no tasks exist. The behavior is minimally transparent.

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, front-loaded sentence conveys the essential purpose. There is no redundancy or filler. Every word contributes meaning.

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?

For a simple list operation with well-documented parameters, the description plus schema covers the basics. However, without an output schema or annotations, it does not address expected return format, side-effect-free behavior, or distinctions from sibling A2A and messaging tools. The context is adequate but not thorough.

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?

The input schema covers all parameters with descriptions and constraints (role enum, limit max 100, offset default 0). The description adds no additional parameter semantics beyond the word 'pagination', which is already explicit in the schema. This aligns with the baseline of 3 for high schema coverage.

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 a specific action ('List') on a specific resource ('A2A tasks') with a meaningful qualifier ('for an agent with pagination'). It distinguishes from siblings like a2a_get_task (single task) and a2a_submit_task, though it doesn't explicitly name alternatives.

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?

The description offers no explicit guidance on when to use this tool versus alternatives. It does not mention that a2a_get_task is for retrieving a single task, that a2a_cancel_task is for cancellation, or that msg_* tools handle messaging rather than A2A tasks. The only implicit guidance is the word 'list'.

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