wordpress_get_system_info

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the return categories (versions, limits, configuration) but does not mention that the operation is read-only, what could happen if privileges are insufficient, or any other behavioral traits. This is a notable gap.

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, direct sentence that immediately states the action, resource, and key content categories. It contains no filler or redundant wording, earning a perfect score for conciseness.

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?

While the description conveys the general purpose, it is vague about the exact scope of 'system information' and does not clarify how it differs from closely related sibling tools. With no output schema, an agent might still be uncertain about the exact structure of the returned data. This is adequate but not thorough.

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 and the schema is empty, so the description has no parameter details to add. Per the baseline for zero-parameter tools, a 4 is appropriate since there is nothing omitted.

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 uses the specific verb 'Get' with the resource 'system information' and elaborates with '(versions, limits, configuration)', making the core purpose clear. However, it does not differentiate from sibling tools like wordpress_get_site_info or wordpress_get_settings, so it misses the full 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?

No guidance is provided on when to use this tool versus alternatives such as wordpress_get_site_info, wordpress_get_settings, or wordpress_get_version_info. The description gives no context for selection, leading to potential ambiguity.

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