Get PHP Info

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

The description states that the tool returns the full phpinfo() output, which is a clear behavioral outcome. However, since no annotations are provided, the description carries the full burden and does not elaborate on output format (e.g., raw HTML), potential side effects, or requirements beyond the parameters, resulting in a moderate transparency 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, concise sentence ('Get full phpinfo() output.') that is front-loaded with the action and resource. Every word adds value, with no redundancy or unnecessary detail.

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?

The tool is simple and the description adequately explains the output, but it lacks differentiation from the sibling hosting_php_details and provides no usage context. The absence of an output schema and annotations means the description alone is not fully complete for an agent to make an informed decision.

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 already provides descriptions for both parameters (domain: 'Website domain', username: 'Hosting account username') with 100% coverage. The description does not add any additional semantic meaning or usage details for the parameters, so the baseline score of 3 applies.

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 (Get) and the resource (full phpinfo() output), making the purpose specific. However, it does not differentiate from the sibling tool hosting_php_details, which could also provide PHP-related information.

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 hosting_php_details or hosting_php_update_*. There is no mention of exclusions, prerequisites, or preferred scenarios, leaving the agent without usage context.

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