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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint, so the 'Read-only' line is redundant. The description earns credit by disclosing that results are dynamically scoped to the caller's entitlements (region, feature flags, build envelope) and that integration options carry the caller's live connection status — behavior an agent cannot infer 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 opens with the verb and resource and then enumerates the payload. It is dense and heavily nested with parentheticals, but every clause carries information, particularly the field list that substitutes for a missing output schema.

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 usefully enumerates the returned shape (key, title, summary, pattern, tools, model role, checklist, integration groups with live connection status) and explains the scoping rules. Missing only minor operational detail such as ordering or pagination behavior for a list tool.

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?

One parameter with 100% schema description coverage, so the enum filter is already documented by the schema. The description mentions 'pattern' only as a returned field, not as the filter parameter, so it adds no meaning beyond the schema. Baseline 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?

Specific verb + resource ('List the Blueprints') with an inline definition of what a Blueprint is (ready-to-run, tested agent configurations) and the fields returned. An agent can distinguish it from create_from_blueprint or get_blueprint by the plural scope, though the singular get_blueprint sibling is never explicitly contrasted.

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?

Usage context is implied by the scoping sentence ('available to this organization and caller', filtered by region/feature flags/build envelope), which tells the agent when results will be narrowed. However, there is no explicit when-to-use versus get_blueprint (fetch one) or create_from_blueprint (instantiate one), so routing is left to inference.

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