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

With no annotations provided, the description carries the full burden of disclosing behavior. It mentions the Authorization header but does not state that this is a read-only listing operation, what the default state filter is, how pagination works, or what the response contains. The behavioral surface is largely undisclosed.

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 short and contains no filler, with the auth note being a legitimate operating requirement. However, the first sentence is a noun-phrase fragment rather than a complete instruction, which slightly detracts from structural clarity.

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 no output schema and no annotations, the description should provide at least a basic idea of return value shape, pagination behavior, or error conditions. It only covers authentication, leaving unfamiliar agents without enough context for correct invocation.

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 all three parameters (after, limit, state) are already documented in the schema. The description adds no specific meaning about how parameters interact or how they shape results, so it earns the baseline score of 3.

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 'Your tasks and their state' names the resource and one aspect of it, but lacks an explicit verb like 'list' or 'retrieve'. The title helps clarify, yet the description alone is too vague to fully define the operation and distinguish it from get_task without relying on context.

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?

No guidance is given on when to use list_tasks versus get_task or other sibling tools. The only mention in the description is the authentication requirement, which is a precondition rather than usage guidance or a context for choosing this tool over alternatives.

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