import_blueprint

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

No annotations are supplied, so the description carries the full behavioral burden for a write/mutation tool, yet it never states the required payload format, whether importing overwrites existing storage, whether the operation is reversible, or what storage scope it targets. The presence of an output schema covers return values, but the mutation semantics remain undisclosed.

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 efficient sentence with the verb and scope front-loaded and no redundant wording. It is under-specified rather than bloated, so brevity is not the problem here.

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 mutation tool with zero annotation coverage, unknown payload format, and a 0%-documented parameter, the description is far too thin. The output schema excuses it from explaining results, but the input contract and storage effects an agent needs before calling it are missing.

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% on the single required parameter 'data', and the description adds no meaning: it does not say whether 'data' is a blueprint string, a JSON document, or an entire book structure. With the whole payload undocumented in both schema and prose, this is a substantive gap for a one-parameter tool.

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 states a specific verb+resource ('Import an exported blueprint or nested book') and names the destination ('bridge-owned storage'), which pairs it clearly with export_blueprint and separates it from capture_blueprint/inspect_blueprint. It does not explicitly name a sibling to route away from, and 'bridge-owned storage' is unexplained jargon.

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 or when-not-to-use guidance, and no mention of prerequisites such as having an exported blueprint first or of what to do if a blueprint with the same name already exists. The implied workflow (export_blueprint → import_blueprint) must be inferred.

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