get_next_task

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

The description discloses that it returns tasks with done dependencies, high priority, and non-done/blocked status. It also mentions optional filters. Although no annotations are provided, the description sufficiently covers behavioral traits for a read operation.

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 concise (two sentences), front-loaded with the purpose, and uses efficient language. Every sentence adds value without redundancy.

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?

The description covers the tool's purpose, considerations, and usage hint. It is complete for a tool with four optional parameters and no output schema, as the return type (tasks) is clear from context.

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% with good parameter descriptions. The description adds value by explaining how parameters (e.g., owner, project) interact with the tool's logic, going beyond the schema alone.

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 states the tool returns the next task(s) to work on based on dependencies, priority, and status. It explicitly distinguishes itself as the key tool for agentic execution, which differentiates it from sibling tools like list_tasks or search_tasks.

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 provides clear guidance by stating 'call this to know what to do next' and explaining the filtering logic. It does not explicitly mention when not to use it or compare to alternatives, but the context is strong.

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