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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, and the description adds substantial behavioral detail on top: pagination with limit capping at 100, has_more/next_page response fields, a warning against partial backlog reads, and the project_id omission side effect. No contradiction with annotations.

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?

Three sentences with no filler: the first states the core function, the second delivers the pagination contract, and the third gives actionable usage guidance. The warning about reading only page 1 is stylized but earns its place by emphasizing a common failure mode.

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 7-parameter paginated read tool with strong annotations, the description is nearly complete: it covers filters, pagination semantics, sequencing before other operations, and project_id fallback. It does not describe the shape of returned task items, but the absence of an output schema is partially mitigated by the disclosed pagination keys and schema-documented task types.

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 coverage is 100%, so the baseline is 3. The description goes beyond the schema by clarifying the pagination boundary (limit caps at 100), the meaning of response pagination fields, and the special behavior of omitting project_id. It also summarizes the filter dimensions, adding real semantic value above the schema.

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 states a specific action ('Lists tasks in one project') with optional filters, making its purpose clear and distinguishable from sibling tools such as get_task (single task retrieval) and get_task_stats (aggregate statistics). It also frames downstream usage before create_task and update_task, reinforcing the tool's role.

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 gives explicit usage context: call this before create_task to find a parent, and before update_task when the id is unknown. It also adds a useful fallback behavior for omitting project_id to discover accessible projects. It does not explicitly name sibling alternatives or state when not to use this tool, so it falls just short of a 5.

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