Block Plugin List

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

No annotations are provided, so the description carries the full behavioral burden and does almost nothing with it. It implies a read-only enumeration but never confirms that, nor does it explain pagination behavior (default page_limit 50) or that results may be truncated.

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 short sentence with no padding, so it is structurally clean and front-loaded. But it is terse to the point of under-specification rather than genuinely concise, leaving obvious questions unanswered.

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?

An output schema exists, so return values need not be explained, but the two undocumented input parameters and the absent annotation coverage leave real gaps. Nothing tells the agent how to filter, how results are paged, or how this differs from block_list.

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% for two parameters. The `filters` parameter is an opaque free-form object with additionalProperties true, and the description gives no syntax, supported keys, or examples; page_limit is only self-documenting via its default. The description adds nothing to compensate.

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?

States a specific verb and resource ('List available block plugins'), which reads clearly against neighbors like block_list (placed blocks) and block_region_list (regions). However, it never names or explicitly distinguishes itself from those siblings, so the agent must infer the difference between a block plugin definition and a placed block.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives such as block_get or block_list. The agent is left to guess whether to call this before block_create/block_place or instead of block_list.

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