Theme Blocks

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

With no annotations the description carries the full burden, and it does well: it discloses the JSON:API source, the returned fields (id, theme, region, label, plugin, weight, enabled state), case-insensitive matching semantics, and the default sort order. It omits explicit read-only framing and any auth/permission requirements, but 'List' reasonably implies a safe read.

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?

Front-loaded with the core action and filter list, then elaborates on semantics. Dense but every sentence adds information; no filler or repetition of the title.

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 structure need not be restated, and the description still usefully names the returned fields. Combined with full parameter coverage and sort-order disclosure, an agent has enough to call it correctly; only sibling disambiguation is missing.

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 coverage is 0%, so the description must compensate, and it does: it explains that 'search' matches label and plugin case-insensitively, and that 'theme_name' and 'region' narrow to a single placement set. All three parameters are given meaning beyond the bare string types in the schema.

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+resource ('List placed blocks') with the optional filters, and the 'block.block.* placement from JSON:API' framing distinguishes placed-block config entities from block plugin/region definitions. It does not name the closest siblings (block_list, block_region_list, block_plugin_list), leaving the agent to infer the boundary.

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?

Offers a concrete use case ('do we have a block like Site branding?') and notes that no filters returns every placement, which implies when to use it. However it gives no explicit when-not guidance and never routes the agent to alternatives like block_list or block_place.

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