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

No BBE behaviors are disclosed. No annotations are present, so the description carries the full burden. It does indicate a read-only listing operation and the 'curated' qualifier implies a preselected set, but it omits details like return format, pagination, or whether the list is exhaustive.

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 a single, tight sentence that front-loads the action and resource and adds the key clarification in a parenthetical. It contains no verbosity, no repetition, and no unnecessary details.

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 parameterless simple listing tool with no output schema and no annotations, this description is complete enough to understand what it does and where it fits: it returns the curated list of electrik/slate-blocks. Missing return-value structure is a minor gap, not a blocker.

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, so there is nothing for the description to explain beyond the schema. The empty schema is fully covered, and the description's mention of resource-specific 'electrik/slate-blocks' adds contextual meaning to the tool's role even though it doesn't address parameters.

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?

Description uses a specific verb ('List'), names the exact resource ('electrik/slate-blocks'), and clarifies what these are with 'curated Blade sections on the docs gallery'. This clearly distinguishes the tool from list siblings like list_components and from the more granular get_* tools.

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 is implied by the noun and verb: when you want to list blocks, use this tool. However, no explicit when-to-use or when-not-to-use guidance is given, and it doesn't explicitly contrast with list_components or the get_* siblings. The intended context is inferable but not stated.

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