GTD: Engaged Tasks

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

No annotations are present, so the description carries the full burden. It discloses the filtering criteria (priority 5, overdue, due today) but does not describe return format, sorting, or any side effects. Adequate for a simple read tool but not rich in behavioral context.

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 one concise sentence, front-loaded with the action and resource, with clear criteria and a rationale (GTD). No waste.

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 tool is simple with no params, no output schema, and no annotations. The description fully captures the filtering logic, but does not clarify the relationship to overlapping sibling tools (e.g., combining due today, overdue, and priority filters), which is a minor gap.

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, so the description holds no burden for explaining parameter meaning. Baseline of 4 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?

The description clearly defines the tool's purpose: retrieving tasks requiring immediate engagement, explicitly enumerating criteria (priority 5, overdue, due today). This distinguishes it from sibling tools like get_tasks_due_today or get_overdue_tasks by combining them.

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 does not explicitly state when to use this tool instead of alternatives like get_tasks_due_today or get_overdue_tasks. It implies usage through the GTD context and criteria, but lacks explicit 'when to use' or exclusion guidance.

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