Erstelle WordPress Post

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

With no annotations, the description must carry the burden of behavioral disclosure. It only states the action (creates a post) and does not mention authentication requirements, side effects, default status, or what happens on success. The output schema exists but does not cover behavioral traits like permission needs or irreversible actions.

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 with no fluff, directly stating the purpose. It is concise and front-loaded. Though it lacks additional context, it is not bloated or padded, so it earns a high score for conciseness.

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 output schema covers return values and the schema covers parameters, the description only needs to clarify purpose and usage. It does that minimally but lacks any context about when to use it, default behavior, or relationships to sibling tools. For a tool with 7 parameters and no annotations, it is adequate but not complete.

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%, so the schema documents all parameters with descriptions. The description itself adds no parameter-level information beyond what the schema already provides, which meets the baseline for high coverage.

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 'Erstellt einen neuen WordPress-Beitrag' uses a specific verb (erstellt) and resource (neuen WordPress-Beitrag), clearly distinguishing this from update/delete tools and from page/product creation. It is direct and unambiguous.

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 like wp_create_page or wp_update_post. There are no use cases, exclusions, or context that would help an agent decide between this and similar tools.

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