save_baseline

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

With no annotations, the description carries full burden. It discloses that the tool runs multiple audits (screenshot, accessibility, performance, Lighthouse) and saves results to a specific file. It also notes it is free and runs within Claude Code. However, it does not mention prerequisites (e.g., app must be running) or failure modes.

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 sentences, front-loaded with purpose, then details, then usage context. The promotional line about being free is slightly extraneous but does not detract. Overall efficient.

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 2 parameters, no output schema, and a description that explains what the tool does, its output file, and when to use it, the description is fairly complete. It could mention the connection to 'compare_to_baseline' but is 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 coverage is 100%, so the description adds value by explaining that `url` must be of a running application and that `codeDir` defaults to cwd. This provides context beyond the schema descriptions.

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 verb 'Save' and the resource 'baseline snapshot', and explains it runs multiple audits. It implicitly differentiates from siblings like 'compare_to_baseline' by establishing a baseline, but does not explicitly distinguish from other audit tools like 'lighthouse_audit'.

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 provides usage context: 'Use this to establish a baseline before making changes, so you can compare later.' This implies when to use but does not mention when not to use or explicitly name alternative tools (e.g., 'compare_to_baseline' for comparison).

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