blueprint_create_blueprint_from_mapping

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

Annotations already declare this as a non-read-only, open-world, non-idempotent write operation, so the description needn't repeat that. It adds minor context about the source of the configuration but does not describe side effects, permissions required, or what happens on success/failure.

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 purpose is front-loaded in the first sentence, but the second sentence merely repeats the endpoint already present in the title and annotations. That repetition does not earn its place, reducing conciseness.

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?

With no output schema, the description should ideally explain return values or key behavioral outcomes, which it does not. It provides the minimal context needed to understand the operation but leaves gaps about return values and error behavior given the nested request body.

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 the schema fully documents both parameters (body and apiVersion). The description offers no additional parameter-level detail beyond the schema, making the baseline score of 3 appropriate.

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 ("Creates") and resource ("a blueprint from a Terraform blueprint configuration"). The parenthetical source endpoint distinguishes it from sibling tools like blueprint_create_blueprint, though it stops short of naming the mapping 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?

The phrase "obtained from /create-blueprint-mapping" implies a prerequisite workflow step, but the description does not explicitly say when to use this tool versus alternatives or state any exclusions. The usage context is present but must be inferred.

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