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

The readOnlyHint annotation already signals a safe read operation概, and the description adds transparency by specifying exactly what will be returned: each block's name, title, dependencies, and the `npx cronus-ui add <name>` install command. No hidden destructive or mutating behavior is suggested.

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 front-loaded with the core purpose ('List the installable Cronus UI blocks'), then immediately adds precision with the registry type and examples, followed by the return contents. It is compact, informative, and free of filler.

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-parameter read-only list operation, the description covers what is listed, what category it belongs to, what kind of items are included, and what fields the response contains. There is no pagination or edge-case note, but those are not essential for this simple catalog query.

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 input schema has no parametersuse, and schema coverage is 100%, so there are no parameter semantics to document. The baseline for a zero-parameter tool is 4; the description adds relevant output meaning without needing parameter detail.

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 states a specific verb and resource ('List the installable Cronus UI blocks'), defines the registry item type, gives concrete examples (hero, pricing, login, dashboard), and distinguishes blocks from components via 'larger, composed sections'. This differentiates it from sibling tools like list_components.

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 intended use is clear: call this tool to enumerate installable blocks and get their install commands. It does not explicitly say when to prefer a sibling tool, but the narrow scope and installation focus provide enough contextual guidance for an agent.

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