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

Annotations cover the safety profile (readOnly=false, destructive=false, idempotent=false), and the description usefully adds behavior beyond that: it fills the private fields of the live baseline when is_current is set, and it consumes a metered monthly allowance. It doesn't say what happens on repeated saves or whether an existing draft with the same name is overwritten.

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?

Two sentences, zero waste, with the core action front-loaded and the quota caveat last. Nothing is repeated from the title or schema.

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 9-parameter mutation with no output schema and full schema coverage, the description supplies the two things the schema can't: the live-baseline side effect and the quota cost. Remaining gaps (overwrite semantics, response content) are minor against complete parameter docs and explicit annotations.

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 baseline is 3. The description does add real meaning for is_current ('fills the private fields of the live baseline') beyond the schema's 'copy live in the store today', but says nothing about the other eight parameters or the optionality of name.

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?

States a specific verb and resource ('Save listing copy as a named draft for a tracked application') plus an operational nuance (marking the copy live today). It is clearly distinct from read/list siblings like list_metadata_drafts and compare_metadata_draft, though it does not explicitly name an alternative.

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?

Usage is only implied: the description tells you what saving accomplishes and that it consumes the monthly draft-save allowance, which nudges toward sparing use. It never states when to prefer this over simulate_metadata or compare_metadata_draft, or any prerequisite like having an existing baseline.

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