Liste WordPress Benutzer

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does mention that appropriate permission is required, which is useful context. However, it does not describe any other behavioral traits such as whether the list is paginated, sorted, includes metadata, or whether it is strictly read-only. This is minimal disclosure for a tool that may expose sensitive user data.

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 extremely concise, consisting of one short sentence and a parenthetical. Every word serves a purpose—the action and the permission requirement. It is well-structured and front-loaded.

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?

Despite having an output schema and no parameters, the description leaves out important context. It does not clarify how this differs from 'admin_list_users' or whether it returns the same result. It also lacks any mention of response format or scope limitations beyond 'all'. For a simple tool this may be acceptable, but the ambiguity with sibling tools makes it incomplete.

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 has zero parameters, so there is no parameter information to clarify. The description does not need to add parameter semantics. Baseline 4 is appropriate because the tool takes no arguments.

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: 'Zeigt alle WordPress-Benutzer an' (shows all WordPress users). It uses a specific verb and resource, and adds scope ('all'). However, it does not differentiate from the sibling tool 'admin_list_users', which likely also lists users.

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 like 'admin_list_users'. The only additional note is the permission requirement, which is a prerequisite, not a usage guideline. No exclusions or alternative recommendations are given.

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