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

The annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the safety profile is largely covered. The description usefully adds that the artifact is non-canonical and does not constitute a decision or execution authorization, but it says nothing about the consequences of the non-idempotent flag (e.g. that repeated saves create distinct artifacts) or about retention/visibility of what is stored.

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, no filler, and the definitional statement precedes the constraint. Each clause adds information an agent cannot get from the 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 six-parameter write tool with no output schema and no parameter documentation, the description covers intent and the decision/execution boundary but leaves the return value (presumably an artifact id), the meaning of `contextDigest`, and duplicate-save behavior unaddressed. It is adequate at the conceptual level and thin at the operational level.

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 six parameters, five of them required, so the description must carry the load. The content-kind list loosely maps to the `kind` enum, but nothing explains `contextDigest` (a required, 200-char string), `projectId` format expectations, `sourceRefs`, or the 200k-char `text` limit — an agent must guess at the most consequential required field.

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") plus a resource ("WORKING artifact") and enumerates the accepted content kinds (plan, interpretation, critique, draft, specialist result), which lets an agent distinguish it from read_work_artifact and list_work_artifacts. It also distinguishes the artifact from canonical research decisions, though it never names a sibling tool directly.

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?

"Use for durable ResearchPilot continuity" gives a positive trigger, and "this never accepts a research decision or authorizes execution" gives an explicit exclusion. It stops short of naming which tool should be used instead for decisions or execution authorization, so the routing on the negative side is implied rather than complete.

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