WPML Post-Übersetzungen abrufen

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states that it retrieves translations, but does not mention read-only safety, required permissions, error behavior (e.g., no translations found), or what the response structure looks like. This is a minimal level of transparency for a tool with zero annotation support.

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 that directly states the tool's purpose without any wasted words or redundant information. It is appropriately sized for a simple getter 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 there is no output schema and no annotations, the description fails to provide essential context such as the format of the returned translations, whether the original post is included, or how missing translations are handled. For a tool with one parameter, the description is minimal but does not fully cover what the agent needs to know about the response.

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 100% (postId is documented as 'Post-ID'). The description adds no additional parameter meaning beyond the schema, so the baseline score of 3 applies per the rubric when schema coverage is high.

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 tool's function: 'Ruft alle Übersetzungen eines Posts ab' (retrieves all translations of a post). This is a specific verb+resource combination that distinguishes it from sibling tools like wpml_get_string_translations or polylang_get_post_language.

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 such as wpml_create_translation or other translation-related tools. There is no mention of prerequisites, exclusions, or alternative tools, leaving the agent to infer usage solely from the name and short description.

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