Cache leeren

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

No annotations are provided, so the description carries the full burden. It only mentions that the operation is conditional on REST availability, but does not warn that flushing cache is destructive to cached data or may temporarily impact performance. Also, the description's focus on 'Object Cache' conflicts with the parameter's broader 'all' and 'transients' options, adding confusion.

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, front-loaded with the action and resource, and contains no redundant phrasing. Every word earns its place.

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?

The description is too sparse for a tool with a parameter and no output schema. It omits behavior on success/failure, side effects, and the meaning of the three cache type options. The REST-availability caveat is helpful but insufficient for an agent to understand the full impact of invoking this tool.

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 schema fully documents the parameter with an enum and description, but the tool description does not elaborate on the differences between 'all', 'transients', and 'object'. In fact, it narrows the tool to 'Object Cache', potentially misleading an agent about what 'all' or 'transients' do. The description adds no value beyond the schema and may even contradict it.

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 the action ('Leert' = clears) and the target resource ('WordPress Object Cache'), with a conditional scope ('falls verfügbar via REST'). This is specific and distinguishes it from sibling admin tools, none of which flush cache.

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 explicit usage guidance or alternatives are provided. The condition 'if available via REST' implies a prerequisite, but there's no 'when to use' or 'when not to use' direction. The context is merely implied by the action.

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