zen_wake_tab

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

No annotations provided, but the description explains idempotency, behavior when tab is alive vs. unloaded, and that it waits for page load. This is transparent for a wake operation.

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: two paragraphs plus a bulleted arg. No fluff, front-loaded with the main action. Efficiently structured.

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?

No output schema, but the description covers the key behavior and uses case. Lacks explicit return info but is adequate for a simple wake command.

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 has 0% coverage but description adds 'The tab ID to wake (get IDs from zen_tabs)'. This provides meaningful context beyond the integer type, compensating for the lack of schema description.

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 'Revive a tab that Zen's Tab Unloader may have discarded' with a specific verb and resource. It distinguishes from siblings by mentioning zen_keep_alive as an alternative for repeated use.

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?

Explicit guidance: 'Use before targeting a tab that might have been idle for a while. Prefer zen_keep_alive for tabs you'll touch repeatedly.' This covers when to use and when to use an alternative.

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