list_tasks

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

No annotations provided. The description states it returns a list of tasks, but does not disclose pagination behavior (e.g., that it returns one page at a time) or other side effects. The output schema partially compensates.

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 brief, with one sentence stating purpose and a bullet list for parameters/returns. However, the parameter list is redundant with the schema, slightly reducing efficiency.

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?

The description fails to mention pagination details (page, limit) that are critical for using this tool correctly. It also omits authentication or rate limit info. However, output schema adds some completeness.

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 description does not add significant meaning beyond the input schema, which already describes each parameter (e.g., list_id, pagination, status filter). Baseline 3 due to 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 'List tasks in a list with optional filtering', using a specific verb ('list') and resource ('tasks in a list'). It distinguishes from sibling tools like create_task, delete_task, and get_task.

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 implies usage for listing tasks with filtering, but lacks explicit guidance on when to use this tool vs alternatives (e.g., get_task for a single task). No exclusions or prerequisites are mentioned.

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