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

Annotations declare this is a non-read-only, non-idempotent, open-world write. Beyond that the description adds a genuinely useful behavioral fact the annotations do not convey: revision conflicts are handled automatically with one retry, so the agent knows a failed save may self-heal once. It still doesn't say whether an existing graph is overwritten or a new revision created, which matters for a non-idempotent mutation.

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 short sentences with no filler; the core action is front-loaded and the retry behavior follows immediately as supporting detail.

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?

Annotations cover the safety profile and an output schema exists, so return values need not be explained. The description supplies the retry semantics and the canvas-visibility outcome, leaving only overwrite-vs-new-revision behavior unaddressed for a mutation that is explicitly non-idempotent.

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 100%, so all four parameters (name, subject, project_id, train_graph) are already documented in the schema; the description adds no syntax, format, or constraint detail beyond it. Baseline 3 is appropriate when the schema carries the full parameter burden.

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 a pipeline graph into a project') plus the observable effect ('visible on the studio canvas'), which separates it from read-side siblings like project.load. It does not explicitly distinguish itself from project.create or pipeline.export, so it stops short of a 5.

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?

Implicit context is present – the parenthetical about canvas visibility hints this is the persistence step after building a graph – and the schema points at project.create/project.list for obtaining a project_id. However, there is no explicit statement of when to prefer this over project.load or pipeline.export, so usage remains inferred rather than stated.

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