blueprint_get_blueprint_request_execution

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false. The description mainly restates that this is a GET that returns details, without adding behavioral context such as whether the execution may be in progress or what operational state it exposes.

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 purpose in the first line. The second line duplicates the endpoint already present in the annotations title, so it is slightly redundant but still compact.

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 simple read-only GET with full schema coverage and rich annotations, the description is minimally sufficient. However, in a large sibling set it does not explain when to choose this execution-details endpoint over the request-details endpoint.

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 requestId, expand, and apiVersion are already documented in the schema. The description adds no extra parameter semantics, which is acceptable at baseline when the schema does the work.

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 and resource: returns request execution details. The word 'execution' distinguishes it from a generic blueprint request lookup, but it does not explicitly name or distinguish it from siblings such as blueprint_get_blueprint_request.

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 guidance on when to use this tool versus blueprint_get_blueprint_request or the resource-plan siblings. The endpoint path implies a GET, but it does not explain when execution details are the right target.

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