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

The description discloses almost no behavioral traits beyond its basic purpose. It does not state whether the tool is read-only, whether it mutates task state (e.g., marks as in-progress), or what the return value contains. Annotations provide no safety hints, so the description carries the full burden and fails to address side effects or output format.

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 concise sentence that gets straight to the point. It is front-loaded with the core concept and contains no unnecessary words.

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?

With no output schema and minimal annotations, the description is the only source of contextual information. It tells the agent what the tool returns (the next task) but omits critical details like whether the operation is safe, how results are structured, or any prerequisites. For a simple tool this might be tolerable, but the lack of behavioral disclosure makes it incomplete.

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?

The input schema has zero parameters, and the baseline for no parameters is 4. The description correctly avoids mentioning parameters, so no additional meaning is needed or provided.

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 identifies the tool as returning 'the next task assigned to the agent', which distinguishes it from sibling tools like tasks_list (which lists all tasks) by focusing on a single actionable item. However, it doesn't explicitly contrast with alternatives or specify whether it returns one task or a set, so it's not a perfect 5.

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?

There is no guidance on when to use this tool versus alternatives like tasks_list or tasks_get. The phrase 'what to work on now' implies a context, but the description does not state exclusions or compare with other task tools, leaving the agent without clear selection criteria.

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