create_blueprint

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=true, so the mutation/safety profile is covered. The description adds that it returns created metadata with an assigned id, but says nothing about auth requirements, side effects, or what happens on duplicate names.

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?

The description is short and front-loads the core action in the first sentence, with the Args block adding useful detail. The boilerplate Args formatting and the README pointer are mild filler but nothing is padded.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. However, for a tool whose main argument is a large free-form blueprint payload, delegating the essential structure to an external README leaves the description incomplete for an agent that cannot open it.

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% at the top level, so the description must compensate, and it does: it defines both required params, explaining 'name' as a display name and enumerating the contents of the 'data' payload (nodes, edges, groups, surfaces, text, icons, connectors, theme, projection). It stops short of detailing payload syntax, deferring to the README.

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 opens with a specific verb+resource ('Create a new Cloudcraft blueprint'), which cleanly separates it from the list/get/update/delete siblings. It does not, however, explicitly name or contrast itself with those siblings.

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 statement of when to use create_blueprint versus update_blueprint or any other sibling, and no prerequisites or preconditions. The only guidance is 'See README for a minimal example,' which is a pointer rather than usable instruction.

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