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

Annotations declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, fully clarifying side-effect behavior. The description's 'List' aligns with read-only semantics, and an output schema exists.

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 a single efficient sentence, and the schema is well-structured with additionalProperties=false. No redundant or confusing text.

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 tool provides full parameter coverage, required vs optional distinction, annotations, output schema, and clear pagination/filtering. Sibling context confirms it is the canonical list-tasks operation.

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 8 parameters have schema descriptions with 100% coverage, including examples, formats, defaults, and constraints (e.g., limit 1-50, status e.g. 'In Progress'). The meaning is clear without ambiguity.

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 tasks in a project with optional filters and pagination, matching the tool name and distinguishing it from singular get_task. It specifies the resource (tasks) and scope (in a project).

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 explains when to use the tool (to list tasks with filters), and the schema provides detailed descriptions for all 8 parameters including defaults for page/limit and required projectKey. It lacks explicit sibling comparison but the purpose is unambiguous.

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