WordPress Suche

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

There are no annotations, so the description carries the full burden for behavioral transparency. It only describes the search scope and examples, but does not indicate whether the operation is read-only, how results are ordered or paginated, or any required permissions. This leaves the agent without critical operational context.

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, concise sentence with no unnecessary words. It is front-loaded with the core action and scope, making it easy to parse quickly.

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?

For a simple search tool with a fully described schema and an output schema, the description is minimally adequate but lacking in usage context and behavioral details. It does not explain the meaning of 'all WordPress content' beyond examples, nor does it address error cases or limitations.

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 input schema already provides descriptions for all four parameters with 100% coverage, including enums for 'type'. The description adds no additional parameter-level meaning beyond what the schema gives, so the baseline of 3 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 states 'Durchsucht alle WordPress-Inhalte (Posts, Pages, Terms, etc.)', which clearly identifies a search action over WordPress content types. It is specific and understandable, though it doesn't explicitly contrast with sibling tools like rest_api_execute, relying instead on the verb 'search' for differentiation.

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 about when to use this tool versus alternatives. It merely states what it does, without clarifying when it should be selected over other content-listing or REST API tools, nor does it mention any exclusions or alternative approaches.

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