squire

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

With no annotations provided, the description carries full burden. It successfully discloses key traits (headless, offline, sandboxed, optional artifact download) but fails to clarify the execution model, persistence, or what the tool returns (success codes, paths, console output?).

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?

Single, well-structured sentence front-loaded with the core action. Every clause earns its place: engine type (headless Chromium), environment (constrained offline sandbox), and side effects (artifact downloads). 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?

Adequate for a tool with 8 parameters and no output schema, covering the sandbox environment and artifact generation. However, given the lack of annotations and output schema, it should disclose return values or execution results to be complete.

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 coverage is 100%, establishing baseline 3. The description adds semantic context by linking 'download screenshots' to the screenshot and download_artifacts_dir parameters, and 'offline' to the url parameter's file:// restriction, but does not elaborate beyond schema definitions.

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 the specific action (Run headless Chromium), environment (constrained offline sandbox), and capabilities (download screenshots/artifacts). It distinguishes from siblings by specifying browser automation in a sandboxed, offline context.

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 'offline sandbox' constraint implies boundaries (file:// URLs only), but there is no explicit guidance on when to use this versus alternatives, prerequisites for the script parameter, or warnings about the timeout behavior.

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