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

readOnlyHint=true already tells the agent this is a safe read, lowering the bar. The description implicitly confirms there is no server-side filtering (returns everything, then filter), which is modestly useful behavioral context, but it says nothing about volume, scoping, or what "details" comprises.

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?

Two short sentences, front-loaded with what the tool returns. The second sentence is slightly awkward in its third-person phrasing but still carries unique information, so it earns 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?

With an output schema present, the description needn't enumerate returned fields, and with no input parameters there is little surface area to cover. The safety profile comes from annotations. Only the relationship to stack creation and the (un)bounded result size go unmentioned.

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?

The tool takes zero parameters, so the schema leaves nothing to explain. The description actually adds a useful clarification: filtering is done by the caller on the returned set, not via an input parameter, which preempts a plausible misread of the empty schema.

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?

"List all available blueprints with their details" gives a specific verb (list) and resource (blueprints), and there is no other blueprint-listing sibling to confuse it with. It doesn't need to distinguish itself from CYCLOID_BLUEPRINT_STACK_CREATE explicitly, but it also offers no hint that blueprints relate to stack creation.

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?

The only usage remark is "The LLM can filter the results based on user requirements," which describes post-hoc filtering rather than when to call this tool. Nothing says when to prefer it over siblings like CYCLOID_CATALOG_REPO_LIST or how it pairs with CYCLOID_BLUEPRINT_STACK_CREATE.

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