Liste WordPress Seiten

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only restates the action 'Holt eine Liste' without detailing pagination, default status, filtering behavior, or whether it returns hierarchical structure, offering no transparency beyond the tool name.

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 unnecessary words, making it concise. However, it adds minimal information beyond the tool name, so it doesn't fully earn its place; it's short but under-specifies the tool's capabilities.

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?

Although an output schema exists, the tool has four parameters with low schema coverage and no usage guidance. The description does not address filtering, pagination, or default behavior, making it incomplete for a tool with this complexity and for distinguishing among many list tools in the 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?

Schema description coverage is only 25% (only 'parent' has a description), and the description itself adds no explanations for 'search', 'status', or 'per_page'. It fails to compensate for the low schema coverage, leaving three parameters semantically unexplained.

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 verb 'Holt' (fetches) and resource 'Liste aller WordPress-Seiten' (list of all WordPress pages), directly matching the tool name and distinguishing it from sibling tools like wp_list_posts and wp_list_categories. The scope is explicit ('aller'), and the purpose is 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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention that this is specifically for pages, nor does it reference sibling tools like wp_list_posts, leaving the AI agent without contextual selection criteria.

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