Run scraper

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

Annotations already indicate destructiveHint=true and openWorldHint=true, which the description does not contradict. The phrase 'hot-load' adds some behavioral context, but the description does not elaborate on side effects, state changes, or error conditions beyond what annotations provide.

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 two sentences, front-loaded with the primary action, and contains no fluff. Every word earns its place.

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 the tool's complexity (7 parameters, mutable, destructive, open world, output schema exists), the description is too brief. It does not explain what 'hot-load' means, mention required parameter 'name', describe return values, or address error conditions. An output schema is present but not referenced.

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 repeats the constraint 'new_tab requires url' which is already in the schema's description for new_tab. It does not add meaning for the other five parameters (name, params, headless, timeout_seconds, tab_id). With schema description coverage at 29% (though the schema itself has descriptions), the tool description fails to compensate for the gap.

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 uses a specific verb ('run') and resource ('saved scraper'), and includes a constraint on parameter usage. It clearly distinguishes from sibling tools like scraper_list, scraper_get, and scraper_save, as well as browser tools.

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 mentions using 'either url or tab_id' and that 'new_tab requires url,' which provides some parameter guidance. However, it does not specify when to use this tool versus alternatives (e.g., browser_open), nor does it mention prerequisites like the scraper must already be saved.

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