Save scraper

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

Annotations already signal destructiveness. The description adds 'validate' and 'atomically', disclosing safety guarantees beyond the annotation. Missing are details on conflict behavior when expected_revision mismatches.

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 sentence of 8 words, front-loading the core action. Every word is meaningful with no 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 presence of an output schema and well-documented parameters, the description is mostly complete but could be strengthened by mentioning what happens on validation failure or revision mismatch.

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?

With schema description coverage at 67% (and all parameters having informative schema descriptions), the tool description adds little parameter-specific meaning beyond the atomic/validation context. Baseline 3 is appropriate.

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 'save' with 'Validate and atomically' adding precise semantics. It clearly distinguishes from sibling scraper tools (list, get, run) which serve different purposes.

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 usage context (saving scrapers for runs), but does not explicitly state when to use this tool versus alternatives, nor provide when-not or prerequisite conditions.

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