Get Flagged Tasks

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

The description thoroughly explains behavior beyond annotations: default values, constraints (limit 1-500, tags max 20), conditional logic (tagMatchMode only applied when tags provided), and examples. Annotations confirm read-only, idempotent, non-destructive, so no contradictions.

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 very concise and well-structured: clear purpose, then Args, Returns, Examples. No fluff, every sentence adds value. Front-loaded with the main goal.

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 low complexity, full parameter documentation, and no output schema, the description is complete. It covers what the tool returns, all parameters with defaults, and example invocations. No missing information for an agent to use it correctly.

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 descriptions, but the tool description adds value by organizing parameters in a clear list and providing examples that show typical usage patterns (e.g., empty object for active tasks, includeCompleted: true). This enhances understanding beyond 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 'Get all flagged tasks in OmniFocus' with a specific verb and resource. It distinguishes itself from sibling tools like omnifocus_get_due_tasks by focusing solely on flagged 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 implies usage when flagged tasks are needed but does not provide explicit guidance on when to use this tool over alternatives. No when-not-to-use or comparison with sibling tools.

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