save_draft_review_artifact

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

The annotations declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the description's job is to add context. It does disclose that writing happens to a local output directory, but it never mentions the overwrite behavior (the schema has an 'overwrite' param defaulting to false) nor what happens to existing files—material for a destructive write.

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?

A single tight sentence that front-loads the core action and destination before listing optional variations. No filler, though the trailing 'publication-style markdown profile support' phrasing is slightly opaque.

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?

For a destructive, 14-parameter mutation tool, this description is far too thin: no overwrite semantics, no parameter explanations, and no routing against sibling artifact tools. An output schema exists so return values need not be covered, but the call-side gaps remain significant.

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 description coverage is 0% across 14 parameters, so the description must carry the burden. It only gestures at three of them (subdirectory, filename override, profile) and says nothing about draft_id, version_id, overwrite, format, or the assay/stressor limit and hitcall thresholds—most parameters remain unexplained.

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?

Names a specific verb ('render and save') and resource ('draft review artifact') and states the destination ('local artifact output directory'). However, it does not differentiate itself from close siblings like export_draft_review_artifact or list_saved_draft_review_artifacts, leaving the agent to guess which of these artifact tools to pick.

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?

There is no when-to-use guidance and no mention of the sibling alternatives (export_draft_review_artifact, list_saved_draft_review_artifacts). An agent cannot infer from this text when this tool is the right choice versus exporting or listing artifacts.

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