Site Settings abrufen

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

The verb 'Ruft ab' implies a non-mutating read operation, and the examples clarify the scope. However, with no annotations, the description does not explicitly state that no changes are made or describe the output format or error behavior, leaving the agent to infer these details.

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, front-loaded sentence with no filler. The examples in parentheses add valuable specificity without making the text bloated.

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 parameterless read-only tool with low complexity, the description gives a solid mental model by listing example settings. It lacks an explicit return structure, but this is not critical for such a simple operation.

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 are no parameter semantics to clarify. The description's parenthetical examples provide useful information about what the returned settings cover, which is adequate given the absence of parameters.

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 action ('Ruft ... ab' = retrieves) and the resource ('WordPress Site-Einstellungen') with representative examples. However, it does not explicitly distinguish itself from the sibling tool admin_list_settings, so it falls just short of a perfect 5.

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?

There is no guidance on when to use this tool versus alternatives like admin_list_settings or wp_get_site_info. No context, prerequisites, or exclusions are provided.

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