Erstelle WordPress Seite

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 only says 'creates a new page' without mentioning side effects, permissions, default status, or how content is handled. This is insufficient for a mutating tool.

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, short sentence, which is concise and front-loaded. However, it is under-specified for the complexity of the tool, so the conciseness is not paired with adequate 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?

Given the tool has 6 parameters, no annotations, and only a single sentence, the description is not complete enough. It lacks usage context, behavioral caveats, and any guidance on required vs optional parameters. The presence of an output schema helps with return values but does not compensate for the missing 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 description adds no parameter-level meaning beyond the input schema. While the schema covers 67% of parameters with descriptions, the remaining parameters (slug, status) lack descriptions, and the tool description does not compensate for this gap.

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 eine neue WordPress-Seite' clearly states the verb (creates) and resource (WordPress page). It is specific enough to distinguish from related tools like wp_create_post, though it does not explicitly differentiate among siblings.

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_post or wp_update_page. The description only states what the tool does, not the appropriate context or exclusions.

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