Liste REST API Funktionen

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

No annotations are provided, so the description must carry behavioral transparency. It implies a read-only listing operation through 'Entdeckt' and 'Zeigt', but does not explicitly state that it makes no changes, requires no authentication, or what the output size might be. Lacking such details, the agent cannot fully anticipate side effects or access requirements.

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 two short sentences, immediately stating the core purpose and what will be revealed. There is no redundant information or filler, making it highly concise and well-structured.

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 discovery tool with optional filters and an output schema, the description covers the essential functionality. It could be more complete by mentioning that it lists custom endpoints as well or that the results might be large, but given the schema and output schema exist, the description is sufficient.

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?

Input schema has 100% description coverage for both parameters (method and namespace), including an enum for method. The description adds no extra parameter semantics, but the schema already provides the necessary details, so a baseline of 3 is appropriate.

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 that the tool discovers all available WordPress REST API endpoints and shows namespaces, routes, and supported HTTP methods. This uses a specific verb ('Entdeckt') and resource (REST API endpoints), and distinguishes it from sibling tools like rest_api_get_function_details or rest_api_list_post_types.

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 explains what the tool does but provides no guidance on when to use it versus alternatives. There is no mention of scenarios like exploring before executing, or excluding cases where specific post types/taxonomies are needed. This leaves the agent to infer usage from the description alone.

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