task_get

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

Discloses read-only nature, safe to retry, and explains behavior of includeSubtasks, notePreviewChars, verbose, fields, and includeLinks. Covers return value structure and truncation details. No annotations provided, so description fully handles transparency.

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?

Concise, front-loaded with purpose and key guidance. Every sentence adds value without redundancy.

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?

Complete for a single-task fetch: covers all parameters, return values, and edge cases like note truncation. No output schema, but description adequately explains expected response.

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%, baseline is 3. Description adds usage context beyond schema, e.g., how includeSubtasks relates to task_get_many, and note truncation behavior. Slightly exceeds baseline.

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 the tool fetches a single OmniFocus task by persistent ID, with a specific verb and resource. It distinguishes from sibling tools like task_get_many by explicitly stating not to use for multiple IDs.

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?

Provides clear guidance on when to use (known task ID, need full detail), when not to use (multiple IDs, use task_get_many instead), and when to use includeSubtasks (only if subtask detail needed, otherwise use task_get_many).

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