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

With no annotations provided, the description carries the behavioral disclosure burden. It conveys that this is a non-mutating 'List' operation and adds domain context, but it does not mention anything about response shape, ordering, or whether the listing is complete or paginated.

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?

A single, front-loaded sentence which states the action, target, and clarifying context without any filler. Every part 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?

For a no-argument listing tool, the description is nearly complete. It could add a little more detail about what output the caller should expect, such as a list of block names or paths, but the current wording conveys the core intent adequately.

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 has zero parameters, so there are no parameter semantics for the description to explain. The schema already confirms the empty parameter set, and the baseline for a zero-parameter tool is appropriately strong.

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 ('List') and resource ('electrik/slate-blocks'), and clarifies what that resource is with the parenthetical 'curated Blade sections on the docs gallery'. This makes the tool's purpose immediately clear and distinguishes it from the component-oriented siblings 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 description gives clear context for when to use the tool: when listing curated Blade sections from the docs gallery. It does not explicitly exclude alternatives or name when-not-to-use conditions, but for a simple zero-parameter list tool the context is sufficient.

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