omnifocus_get_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 of behavioral disclosure. It says 'Get tasks' but does not describe the response format, default behavior beyond the schema, error cases, or any side effects; 'Detected version: standard' is cryptic and does not meaningfully disclose behavior.

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 first two sentences are compact and front-loaded, making the core purpose immediately clear. However, the third segment, 'Detected version: standard,' is vague and does not earn its place; it adds noise without actionable context.

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?

For a simple read tool with one optional enum parameter, the description is mostly sufficient and the schema covers the parameter details. But with no output schema, it would benefit from stating what a successful response contains, and the unexplained version note leaves a small 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?

Schema description coverage is 100%, and the single parameter is a well-described enum including its default. The description repeats the enum values ('flagged, due today, or all') but adds no additional semantic detail beyond what the schema already provides.

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 states a specific verb-resource pair, 'Get tasks from OmniFocus,' and lists the filter options, making the tool's purpose clear. It distinguishes from 'get_projects' and 'get_config' by the resource, but it does not explicitly differentiate itself from sibling task tools such as 'create', 'update', or 'complete'.

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 intended use is implied by 'Get tasks' and the filter options, but the description gives no explicit guidance on when to use this tool versus the sibling create/update/complete tools. It offers clear context about what it returns, yet stops short of stating exclusions or alternatives.

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