Get Due Tasks

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, destructiveHint=false. Description adds return format ('Array of due tasks sorted by due date'), which is useful but not significantly beyond annotations.

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?

Well-structured with clear Args, Returns, and Examples sections. Every sentence adds value; no redundancy. Concise but informative.

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?

Covers input semantics well and mentions return format. However, without output schema, description of returned task structure is minimal; more detail on fields would improve 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?

Schema coverage is 100%, but description adds value with defaults, constraints (0-365 days, 1-500 tasks), and detailed tagMatchMode explanation. Examples further clarify parameter usage.

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?

Description clearly states 'Get tasks that are due within a specified timeframe' with specific verb and resource. Distinguishes from sibling get-tools (e.g., get_flagged_tasks) by focusing on due dates.

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?

Includes examples for common scenarios (due this week, today, 30 days) which imply usage contexts. However, no explicit guidance on when to use this tool versus alternatives like omnifocus_search or omnifocus_get_planned_tasks.

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