app_window_new_tab

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

With no annotations, the description fully discloses side effects (opens a new tab, no data cache invalidation), possible errors (WINDOW_UNAVAILABLE, WINDOW_OPEN_FAILED), and return value shape. This exceeds transparency requirements.

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 and front-loads the main purpose. It contains several sentences that each provide valuable context, but could be slightly more concise by combining some statements. Still, it is efficient and clear.

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, no output schema, and no annotations, the description covers all necessary aspects: purpose, usage guidance, side effects, errors, and return format. It is fully complete for this simple tool.

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 tool has no parameters, and schema coverage is 100% by default. The description adds nothing extra about parameters, but that is acceptable as there is nothing to add. Baseline 4 is appropriate.

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 opens a new tab on the front OmniFocus window via OmniJS. It specifies the exact resource and action, and distinguishes itself from the sibling tool 'app_window_new' by explicitly stating not to use it for standalone windows.

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 tab or a flow needs an additional view'), warns headless agents not to fire it, and directs to an alternative ('prefer app_window_new instead') for standalone windows.

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