sweep_tabs

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals the key safety behavior that by default it only reports and does not close tabs. However, it does not explain what happens when dry_run is false, any destructive potential, or other side effects. This is useful but incomplete for a tool that can likely close tabs.

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 a single, concise sentence that front-loads the core purpose and emphasizes the critical default safety behavior with bold text. Every element earns its place with no redundancy or unnecessary detail.

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 simple tool with one optional parameter and no output schema, the description adequately covers the primary purpose and the key behavioral default. It does not specify the output format or define what makes a tab 'cleanable', but these are less critical given the tool's simplicity. The description is sufficient to understand the tool's role and main mode of operation.

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 schema has one parameter (dry_run) with no description coverage (0%). The description's mention of "默认只报不关" directly informs the default behavior of dry_run, implying that setting dry_run=false would enable closing. This provides meaningful context for the parameter beyond the schema. It does not fully spell out the exact mapping, but it is sufficient for a single boolean parameter.

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's function: listing tabs that are candidates for cleanup. The verb "列出" (list) and the specific resource "可清理的标签候选" (cleanable tab candidates) make the purpose distinct from siblings like close_tabs and list_tabs. It also notes the default behavior, further clarifying what the tool does.

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 implies a usage context (listing cleanup candidates before potentially closing tabs) but does not explicitly state when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or when not to use it. The phrase "默认只报不关" suggests it's a safe first step, but this is not directly tied to a recommended workflow.

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