blueprint_create_blueprint_mapping

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

Annotations declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false, but the description frames the operation as retrieving/parsing and returning information. That reads as a read-only operation and omits the side effects implied by creating a blueprint mapping, contradicting the mutation annotation.

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 action, but the second line is a raw endpoint path that does not help an agent decide when to call the tool. The first sentence is also misleading about the mutation, so the structure is efficient but not fully effective.

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 nested-body, non-read-only integration endpoint with no output schema, the description does not explain the result, side effects, or usage conditions. The schema is complete, but the behavioral and routing context needed for safe invocation is 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 100%: repositoryId, commitId, sourceDirectory, and apiVersion are all documented in the schema. The description adds no parameter-level semantics beyond 'specified Terraform configuration file(s),' so the baseline 3 is 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 sentence names a specific action and resource: retrieving and parsing Terraform configuration files for blueprint construction. However, it does not describe creating a blueprint mapping as the tool name and endpoint imply, and it does not differentiate from siblings like blueprint_create_blueprint_from_mapping or blueprint_get_terraform_configuration_sources.

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 explicit when-to-use guidance, no prerequisites, and no alternatives named. The phrase 'for blueprint construction' is too vague to help an agent choose between this tool and the many other blueprint_* siblings.

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