delete_baseline

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

No annotations are provided, so the description carries full responsibility for disclosing behavioral traits. It only states that deletion happens, but does not mention whether the deletion is permanent, what happens if the baseline does not exist, or any side effects on associated comparisons. The word 'Delete' implies mutability, but the lack of detail about consequences is a significant gap.

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 long, with the action front-loaded in the first sentence and a brief usage context in the second. Every word contributes to clarity without redundancy or fluff.

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 simplicity (one parameter, no output schema) and absence of annotations, the description conveys purpose and usage but omits important behavioral aspects like permanence or error handling. It is adequate for understanding when to call the tool but not fully complete for anticipating consequences.

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 already provides 100% description coverage for the only parameter 'name' as 'Baseline identifier to delete'. The description merely repeats 'by name' without adding format details, constraints, or examples, so it does not significantly enhance parameter understanding beyond the schema.

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 'Delete a saved baseline by name', specifying the verb, resource, and method of identification. This distinguishes it from sibling tools like capture_baseline, compare_visual, and list_baselines, which perform different operations.

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 a specific condition: 'Use when a page has intentionally changed and the old baseline is obsolete.' This gives clear context for when deletion is appropriate, although it does not explicitly mention when not to use it or name alternative tools.

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