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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It discloses no side effects, read-only status, authentication needs, rate limits, pagination, response shape, or data source behavior. An agent cannot know this is a safe read operation or what calling it will do.

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 but not effectively concise: the first sentence merely restates the tool name, and the second references a URL without explaining what the catalog contains or how it relates to tool behavior. Neither sentence carries meaningful operational value, so the brevity reflects under-specification rather than disciplined conciseness.

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 tool with no output schema and no annotations, the description must explain what the agent should expect upon invocation. It does not mention the returned data, whether it is a list of blueprint names, metadata, or references. The URL hint is not enough to make the tool safely callable, even though the parameter surface is trivial.

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?

There are zero parameters and schema coverage is 100%, so there is nothing for the description to add. The empty input schema already fully defines the parameter surface. This matches the baseline for a no-parameter tool.

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 consists of an identity statement ('MCP-Agents tool list_custom_blueprints') and a reference to a live catalog URL, but never states the verb and resource: that this tool lists custom blueprints. The tool name alone implies the purpose, but the description does not articulate it, making this largely tautological and indistinguishable from the sibling create_custom_blueprint without opening schemas.

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 list_custom_blueprints versus alternatives such as list_vertical_plugins, list_models, or list_deal_workspaces. The only contextual hint is the URL reference, which does not explain selection criteria or exclusions. With zero usage direction, the agent must infer when this tool is appropriate.

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