wordpress_advanced_system_info

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

No annotations are provided, so the description carries the full burden. While 'Get' implies a read-only operation, the description doesn't explicitly confirm this is safe/non-destructive, mention performance implications of 'comprehensive' data gathering, or note any rate limiting or authentication requirements.

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 efficient sentence that front-loads the key information. The '[UNIFIED]' prefix appears to be metadata noise that doesn't add value, but the overall structure is concise with no wasted words.

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?

Since no output schema exists, the description partially compensates by listing specific returned data points (PHP, MySQL versions, etc.). However, with no annotations and undocumented parameters, it lacks complete behavioral and usage context for a system information tool.

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 schema has 0% description coverage for the required 'site' parameter, and the description fails to compensate by explaining what the parameter represents (URL, ID, slug) or its expected format. The parameter is completely undocumented beyond its name.

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 retrieves 'comprehensive system information' and lists specific data points (PHP version, MySQL version, WordPress version, server info, memory limits), which distinguishes it from siblings like 'wordpress_advanced_system_phpinfo' (narrower scope) and 'get_system_info' (generic). However, it doesn't explicitly contrast with these alternatives.

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 provided on when to use this tool versus similar alternatives like 'wordpress_get_site_health', 'wordpress_advanced_system_phpinfo', or 'get_system_info'. No prerequisites or conditions are mentioned.

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