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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true, destructiveHint=false), so the bar is lower. The description adds real value beyond them by disclosing the return shape (title, due date, owner, status) even though no output schema exists, plus the single-filter constraint; it says nothing about pagination limits or total-count behavior, which the schema only partly covers.

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, front-loaded with the filter axis, followed by return fields and endpoint. Nothing is padded and there is no ambiguity to untangle.

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 two-optional-parameter list tool with no output schema, the description supplies the missing return-value information and the filter cardinality constraint. Only pagination/total-result behavior is absent, and that is already visible in the schema.

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 both parameters are already documented, including the enum and the 25-per-page note. The description restates the enum values and adds the "one filter per call" meaning, but this is largely repetition of structured data, so the baseline 3 applies.

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?

States a specific verb and resource ("List tasks") plus the filtering axis and the returned fields, so it is clearly not the single-record get_task or the mutating create_task. It stops short of naming any sibling explicitly to disambiguate.

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?

Usage is only implied: an agent can infer it should call this to enumerate tasks in a given status bucket. The parenthetical "one filter per call" rules out a multi-status request, which is a useful constraint, but there is no stated when-not or pointer to an alternative tool.

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