Liste Template Parts

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

With no annotations provided, the description carries the full burden. It discloses that this is a read-only listing operation ('Zeigt alle Template Parts an'), which implies safety. However, it does not specify whether the list includes all available parts from the active theme or any other scope, nor does it mention any limitations. For a zero-param tool, this is minimally sufficient but not rich.

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 one concise sentence that is front-loaded with the verb and resource, plus useful examples in parentheses. Every word earns its place, and the structure is immediately clear.

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 simplicity (0 params, output schema present), the description covers the core purpose. It could add context about which template parts are included (e.g., 'from the active theme'), but the output schema likely documents the return structure. Overall, it is adequately complete for its complexity.

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?

There are zero parameters, so the schema is trivially covered. The description says 'alle' (all), implying no filtering is possible, which aligns with the empty parameter list. With no params to document, the baseline of 4 applies.

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 uses the clear verb 'Zeigt an' (shows) and explicitly names 'Template Parts' as the resource, with examples (Header, Footer, etc.). This distinguishes it from sibling tools like gutenberg_list_templates, which lists templates rather than template parts.

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?

There is no guidance on when to use this tool vs alternatives. It only states what it does, with no context about scenarios, prerequisites, or exclusions. Sibling tools with overlapping names (e.g., gutenberg_list_templates) are not referenced.

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