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

Annotations only declare a safe read (readOnlyHint, destructiveHint=false, openWorld=false); the description goes well beyond them by enumerating the returned fields, explaining the side effect of selfPersisting blueprints (tables are provisioned in the organization automatically, some extension-owned), and warning never to create a table a blueprint already covers. That is exactly the kind of consequence detail annotations cannot carry.

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?

Front-loaded with the action and the pre-check guidance, and the return-field list plus kind taxonomy are both load-bearing for a tool with no output schema. It is dense and heavy on capitalization/emphasis, and a couple of clauses (the parenthetical functionality list, the restated 'never create a table for a feature it covers') could be trimmed without loss.

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 zero-required-param listing tool with no output schema, the description supplies everything needed: what comes back per blueprint, what selfPersisting implies, the two kinds and which sibling tool consumes each, and how to narrow the result. No material gap remains for an agent deciding whether and how to call it.

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 0%, so the description must carry the single enum parameter, and it largely does: it identifies 'widget-set' as the default returned, 'fbb' as complete apps used with create_flow_from_blueprint, and 'any' as both. It never explains the fourth enum value, 'whole-flow', leaving one value's meaning undocumented in both places.

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 and resource ('List EVERY vetted, type-checked blueprint available to reuse') and immediately scopes what a blueprint is (working functionality, not just screen layouts). It also distinguishes itself in the same breath from search_blueprints, get_blueprint, apply_blueprint_widgets and create_flow_from_blueprint, so an agent can route correctly without opening any sibling schema.

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?

Gives an explicit when ('Check the catalog BEFORE creating custom tables or hand-rolling a capability') and names two alternatives with the condition that selects them ('To find the best match for a specific capability instead of scanning the whole catalog, use search_blueprints'). It also notes get_blueprint's role as read-only inspection, leaving nothing to inference.

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