Parse Gutenberg Blocks

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

With no annotations provided, the description must fully disclose behavioral traits. It states only that the tool parses HTML and extracts block structure, but omits details such as input format expectations (raw HTML vs. serialized block comments), error behavior for invalid content, or whether it handles nested blocks in a specific way. The operation appears read-only, but that is not explicitly stated.

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, compact sentence with the key action and object front-loaded. It contains no filler or repetition, making it highly efficient for an agent to parse.

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?

For a single-parameter parse tool, the description provides a basic 'what' and 'result' but lacks behavioral caveats and usage context. The presence of an output schema somewhat offloads return-value details, but no annotation coverage and minimal behavioral disclosure leave gaps. It is adequate but not comprehensive.

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 100% since the single parameter 'content' has a description ('Der HTML/Block-Content zum Parsen'). The tool description adds context by specifying this is post HTML content, but it does not materially expand on the parameter's meaning beyond the schema. The baseline of 3 is appropriate as the schema already carries the burden.

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 clearly states a specific action ('Analysiert den HTML-Content eines Posts und extrahiert die Gutenberg Block-Struktur') and names the resource (HTML content) and outcome (Gutenberg block structure). It distinguishes itself from sibling tools like gutenberg_generate_block or gutenberg_list_block_types, which focus on creation or listing rather than parsing.

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 given on when to use this tool versus alternatives. It simply describes the function without mentioning preferred use cases, prerequisites, or in which contexts another tool would be more suitable. The lack of any comparative or conditional advice leaves the agent to infer the intended usage.

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