app_window_new

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

Since no annotations are provided, the description fully discloses behavioral traits: it is a UI-affecting tool only meaningful when OmniFocus is running, has no data cache invalidation, returns specific structure, and errors (WINDOW_OPEN_FAILED). This is comprehensive.

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 well-structured with each sentence serving a purpose: action, constraints, usage guidance, return info, errors, side effects, and example. It is front-loaded with the core action and is appropriately sized for the information provided.

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 no parameters and no output schema, the description is complete: it covers purpose, constraints, return shape, errors, and side effects. No additional information is needed for an agent to use this tool 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?

The description explicitly states 'Takes no arguments' and provides an example call with no parameters. With zero parameters and 100% schema coverage, the description adds clarity by confirming emptiness and showing 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?

The description clearly states it opens a new OmniFocus window via OmniJS, using a specific verb ('Open') and resource ('new window'). It distinguishes from sibling tools by explicitly stating it is UI-affecting and not for reading data, directing to task_list or project_list for data queries.

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 provides explicit when-to-use scenarios ('when the user asks open a new window' or 'flow needs a fresh, unfocused OmniFocus window') and when-not-to-use ('Headless agents should not fire this', 'Do NOT use to read task or project data'). It also suggests alternatives (task_list, project_list).

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