Liste alle Taxonomien

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

Since no annotations are provided, the description carries the full burden. The word 'zeigt' (shows) inherently implies a read-only operation, and the qualifier 'mit REST API Support' adds scope. However, it does not explicitly disclose absence of side effects, auth requirements, or pagination, leaving some behavioral aspects implicit.

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, compact sentence that immediately states the action and resource. It contains no filler words and is appropriately sized for the simplicity of the tool.

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 zero-parameter input and the existence of an output schema, the description is complete for a simple listing tool. It specifies the exact scope ('all registered taxonomies with REST API support') without needing to explain return values, which are covered by the output schema.

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 tool has zero parameters, so there is nothing to explain. With an empty input schema, parameter semantics are trivially clear, and the description does not need to add any parameter information. The baseline for 0-parameter tools is 4.

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 function with a specific verb ('Zeigt') and resource ('Taxonomien'), and adds a qualifier ('mit REST API Support') that distinguishes it from other listing tools like rest_api_list_post_types. It is unambiguous and directly addresses what the tool does.

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 implies the tool should be used when needing to display taxonomies with REST API support, but it does not explicitly mention when to use it over alternatives or any exclusions. It provides a clear context of what it returns but lacks guidance on alternatives or prerequisites.

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