wordpress_search_block_directory

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

There are no annotations, so the description must fully disclose behavior. It reveals only the action 'Search' and the target directory, but omits key behavioral details like whether results include block metadata, whether it makes a network request, how results are formatted, or whether it supports filtering beyond the term parameter.

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 that states the primary action and target. There is no redundant or filler content; every word contributes to meaning.

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?

With no annotations, no output schema, and minimal parameter information, the description is too sparse for an agent to confidently invoke the tool. It lacks expected return shape, possible edge cases, or any indication of network dependency or result limits.

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% and there is one required parameter, 'term'. The description adds no meaning beyond the schema's field name; it does not explain what kinds of terms are valid, whether matches are partial or exact, or how the term is used against block names/descriptions/search tags.

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 action and resource: 'Search WordPress.org block directory'. The 'WordPress.org' qualifier differentiates this from local block-related tools like wordpress_get_block_types, though it doesn't explicitly name alternatives or contrast with local block sources.

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 guidance on when to use this tool versus alternatives such as wordpress_get_block_types or wordpress_get_block_patterns. The description only states what it does, not when to prefer it over sibling tools.

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