cortex_get_next_task

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

No annotations are provided, so the description carries full behavioral disclosure burden. While 'Get' suggests a read-only operation, it does not explicitly state that there are no side effects, auth requirements, or rate limits. The description is minimal and lacks detail on what happens if no pending task exists.

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 sentence that is highly concise and front-loaded. Every word serves a purpose: it states the action, the resource, and the behavioral guideline. No unnecessary information is present.

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 the tool's simplicity (no parameters, no output schema), the description is mostly complete. It clearly states the purpose and usage context. However, it lacks information about the return value format or behavior when no pending tasks exist, which would enhance completeness.

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 tool has zero parameters, and the schema coverage is 100%. According to the rubric, 0 parameters yields a baseline of 4, and the description does not need to add parameter information. No further clarification is needed.

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 it retrieves the next pending todo, with a specific verb and resource. It distinguishes its role from sibling tools by emphasizing that the agent always calls this tool and never decides its own next step.

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 explicitly says 'agent always calls this, never decides own next step', which provides clear guidance on when to use this tool. However, it does not mention alternatives or explicitly state when not to use it, though the context implies it is the sole decider.

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