Save blueprint

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

Annotations only state the tool is not read-only and not destructive; the description adds that it persists to a local store and that names are unique, which are useful behavioral details. However, it does not disclose what happens on duplicate names (error vs. overwrite) or what the response contains, leaving some ambiguity for a mutation tool with sparse annotations.

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 front-loaded purpose and no filler. The uniqueness note is compact and the mention of downstream tools is valuable.

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 complex nested blueprint object and lack of output schema and rich annotations, the description covers the core action and uniqueness but omits conflict handling and return value, leaving some gaps for an agent deciding whether saving will overwrite or fail.

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?

The top-level schema has 0% description coverage, so the description must compensate. It adds a uniqueness constraint for the `name` parameter, but provides no additional meaning for `blueprint` or `description` beyond what the schema structure implies, leaving the agent to infer that blueprint is a full server configuration.

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 clearly states the tool saves a blueprint to a local store for reuse, using specific verbs and referencing downstream tools (execute_build_plan, diff_blueprint) that distinguish it from sibling blueprint tools like list, get, delete, and export.

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?

It explains the purpose is reuse, pointing to execute_build_plan and diff_blueprint as follow-up uses, giving the agent a clear context for when to invoke save_blueprint. It does not explicitly state when not to use it or compare to export_server_blueprint, but the guidance is sufficient for basic selection.

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