wordpress_search_block_directory

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

No annotations are present, and the description only says 'Search' without disclosing key behaviors like whether it returns results, pagination, or rate limits. For a simple search, minimal behavioral context is needed, but the description adds nothing beyond the action.

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 sentence, which is concise but overly brief given the lack of parameter and behavioral details. It earns its place but fails to provide necessary information.

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 output schema and minimal input schema descriptions, the description is insufficient for an agent to understand the tool's full behavior. It needs to specify the format of search results and how to interpret the 'term' parameter.

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% (the 'term' parameter has no description), and the tool description does not explain what the parameter means. It should clarify that 'term' is a search query for block names or keywords.

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 'Search WordPress.org block directory', which clearly indicates the tool's action (search) and resource (block directory). It is specific enough to distinguish from general search tools like 'wordpress_search_posts', though it could be more explicit.

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 is provided on when to use this tool versus alternatives. With many sibling tools, the description should indicate context (e.g., 'Use to find blocks from WordPress.org' vs internal searches).

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