camofox_cleanup_idle_tabs

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

No annotations provided, so description carries full burden. It discloses key behaviors: preserves active/queued tabs, never returns sensitive data (URLs, titles, cookies, etc.), and defaults to dry-run mode. Missing details on session handling but sufficient.

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?

Three concise sentences, front-loaded with purpose. Every sentence earns its place: purpose, behavioral constraints, and default mode. No 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?

For a 5-parameter tool with no output schema and no annotations, description explains purpose, behavior, and limitations. Lacks details on session handling (e.g., closeEmptySessions) and return value format, but overall adequate.

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% (baseline 3). Description adds context like 'Defaults to dry-run mode' reinforcing dryRun parameter, and 'proactive memory-pressure cleanup' provides context for minIdleMs/maxTabsToClose. No elaboration per parameter, but schema is complete.

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?

Description clearly states verb ('closes idle tabs') and resource ('tabs') with specific context: proactive memory-pressure cleanup, preserving active/queued operations. Distinguishes from siblings like camofox_close_tab_group or camofox_create_tab.

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?

Description implies use for memory cleanup but does not explicitly state when to use or when not to use, nor provide alternatives beyond the sibling list. No usage exclusions or guidance.

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