wordpress_advanced_system_phpinfo

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. While it lists the types of configuration data returned, it fails to mention if this is a read-only operation, whether it requires elevated permissions, potential security sensitivity of the data, or response format/structure.

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 conveys the core functionality without redundancy. The '[UNIFIED]' prefix is minor metadata noise but does not significantly detract from the overall 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?

Given the absence of annotations, output schema, and parameter descriptions, the description is insufficient. It should disclose behavioral traits (read-only status, auth requirements) and parameter semantics to compensate for the lack of structured metadata.

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 0% and the description completely fails to compensate by explaining the 'site' parameter. There is no indication of what format the site identifier should take (URL, ID, slug) or examples of valid values.

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 'PHP configuration' and specifically lists what is included (loaded extensions, ini settings, disabled functions), distinguishing it from generic system info tools. However, it does not explicitly differentiate from the sibling tool 'wordpress_advanced_system_info'.

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 'wordpress_advanced_system_info', nor does it mention prerequisites (e.g., admin privileges typically required for phpinfo) or when to avoid using it.

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