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

Annotations already establish readOnlyHint/destructiveHint=false, so the trailing 'Read-only' is redundant. However, the description adds meaningful behavioral context beyond the annotations: it details the dynamic content returned, notably the caller's live connection status for integration groups, which is not derivable from the schema.

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 front-loaded sentence that puts the resource first and then lists the returned content. Efficient, with only the redundant 'Read-only' clause not earning its place.

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?

Given no output schema, the description does the heavy lifting by enumerating the return contents, and annotations cover safety. Only minor gaps remain, such as behavior when the key is not found.

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 coverage is 100% and the single 'key' parameter is fully documented with an example and a pointer to list_blueprints. The description adds no further parameter semantics, so the baseline of 3 applies.

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?

States a specific verb (get) and resource (Blueprint) and enumerates exactly what is returned — description, instructions, tools, tests, checklist, integration groups. The word 'One ... in full' implicitly distinguishes it from list_blueprints, but the sibling is never named, so it falls short of a 5.

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?

No explicit when-to-use or prerequisites. The contrast with list_blueprints ('One ... in full') only implies that this is the detail-view counterpart, leaving the agent to infer the selection condition rather than being told it.

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