Block List

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

No annotations are provided, so the description carries the full burden. It does not disclose pagination behavior (default page_limit 50, page_offset 0), filtering support, whether the list is scoped to a context (e.g., current theme or region), or what the response contains. 'List all blocks' is behaviorally opaque for a tool with three parameters.

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, front-loaded sentence with no wasted words. Its brevity, however, comes from omission rather than efficiency, so it earns a 4 for structure but not a 5.

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?

The tool has an output schema, so return-value explanation is not required. But with no annotations, three undocumented parameters, and a crowded sibling set, the description is far too thin. It fails to provide the context an agent needs to invoke it correctly.

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?

Schema description coverage is 0%, so the description must compensate for three undocumented parameters. It mentions none of them: 'filters' is a generic anyOf object, and page_limit/page_offset are undocumented. The description adds no parameter meaning whatsoever.

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 all blocks'), so the purpose is identifiable. However, it provides no differentiation from siblings like block_plugin_list, block_region_list, or block_get, which all deal with blocks in Drupal. An agent cannot tell from this text which block-related tool to pick.

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 this tool versus the numerous block-related siblings. No prerequisites or conditions are stated. The description merely says it lists blocks, leaving the agent to infer usage.

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