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

With no annotations, the description carries the full burden. It does disclose two meaningful traits: results are ordered newest first and results are paginated. It omits permission requirements, whether archived or canceled tasks are included, and what 'this project' resolves to.

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?

Two short sentences with the core behavior front-loaded and zero filler. The only flaw is that the concise second sentence introduces a misnamed parameter, so brevity costs accuracy.

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 4-parameter read tool with no annotations and no output schema, the definition covers purpose, ordering, and pagination but leaves the status/lane filters and the limit default (20, max 100) unexplained. Adequate but with clear gaps an agent would hit in practice.

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 description coverage is only 25% (lane documented; limit, cursor, status not), so the description needs to compensate. Instead it refers to "next_cursor", a parameter name that does not exist in the schema (the parameter is "cursor"), creating a real risk of a malformed call, and it says nothing about lane, status, or limit.

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?

"List this project's tasks" gives a specific verb and resource, and "newest first" states the ordering. It does not explicitly contrast with the sibling get_task, but the list-vs-get distinction is inferable from the verbs.

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 second sentence explains the pagination workflow (pass the cursor from a previous page to continue), which is genuine when-to-use guidance. There is no guidance on when to use this versus get_task, or on how filters affect the result.

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