List tasks

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

With no annotations provided, the description carries the full burden of behavioral disclosure, yet it says nothing about read-only nature, pagination limits (row_count max 100), sorting, filtering, or return format. This is a complete gap for a tool with a complex nested parameter object.

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 sentence is technically concise, but it is under-specified rather than efficiently front-loaded. A single four-word restatement does not earn its place as a tool description for a nontrivial listing operation.

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 nested schema, pagination controls, search criteria, no annotations, and no output schema, the description is completely inadequate. An agent has no information about what the tool returns, how to constrain results, or how it differs from related list tools.

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 single parameter is a nested list_info object with seven sub-properties, but schema description coverage is 0%. The description adds no meaning about row_count, sort_field, search_criteria, or any other field, leaving the agent to infer everything from property names alone.

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 'List tasks.' merely restates the tool name and title, making it a tautology rather than a specific statement of purpose. It does not distinguish this tool from sibling list_request_tasks or explain what scope of tasks is covered.

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?

There is no guidance on when to use list_tasks versus alternatives such as list_request_tasks or get_task. The description supplies no context, exclusions, or routing information.

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