wordpress_parse_blocks

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Parse block content from HTML' but doesn't reveal if this is a read-only operation, what permissions are needed, if it modifies data, or any rate limits. It lacks details on error handling, output format, or side effects, leaving significant gaps for a tool that processes content.

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, efficient sentence with no wasted words. It's front-loaded and directly states the tool's function, making it easy to scan and understand quickly without unnecessary elaboration.

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?

Given the tool's complexity (parsing HTML to block content), lack of annotations, no output schema, and low schema coverage, the description is incomplete. It doesn't explain what the parsed output looks like, any dependencies, or behavioral traits, making it inadequate for an agent to use the tool effectively without additional context.

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?

The input schema has 1 parameter with 0% description coverage, and the description does not compensate by explaining the 'content' parameter. It doesn't specify what type of HTML content is expected (e.g., full page HTML, block-specific markup), any formatting requirements, or examples. This leaves the parameter's semantics unclear beyond its name.

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 'Parse block content from HTML' clearly states the action (parse) and resource (block content from HTML), but it's vague about what 'parse' entails—does it extract, validate, or convert? It distinguishes from siblings like 'wordpress_get_block_types' or 'wordpress_get_reusable_blocks' by focusing on parsing, but lacks specificity on the output or purpose beyond the basic verb.

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. For instance, it doesn't mention if it's for processing raw HTML into WordPress block format, or how it differs from other content-handling tools like 'wordpress_execute_shortcode' or 'wordpress_import_content'. The description implies usage for HTML content but offers no exclusions or prerequisites.

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