Update PHP options

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

The description discloses a non-obvious behavior: values above the account plan limit are silently capped, so a successful request may apply a smaller value. It also advises reading the applied value via the Get PHP details endpoint, which compensates for the lack of output schema. This meaningfully extends the annotations without contradicting them.

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 concise and well-structured: the first sentence states the purpose, the second gives the key usage instruction, and the third provides the critical cap warning and follow-up. Every sentence earns its place with no filler.

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?

Despite having no output schema, the description tells the caller exactly how to verify the applied value, addressing the most important ambiguity. It does not document option value types or valid option keys, but the examples and schema coverage are sufficient for typical usage.

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 documents all three parameters with 100% coverage. The description adds useful examples of PHP option names and reinforces the partial-update behavior, but it does not define the value types or valid option keys inside the nested options object, leaving some ambiguity.

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?

Description states a specific verb and resource: 'Updates PHP options for the website' with concrete examples like `memory_limit`, `max_execution_time`, and `upload_max_filesize`. It also clarifies a partial-update semantic ('Only provide the options you want to change'), but it does not explicitly distinguish itself from similarly named siblings such as agency-hosting_replaceWebsitePHPOptionsV1.

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 explicit guidance on when to use this tool instead of alternative PHP-related tools like hosting_updatePHPExtensionsV1, hosting_updatePHPVersionV1, or agency-hosting_replaceWebsitePHPOptionsV1. The only usage context is about which options to include and a recommendation to call the Get PHP details endpoint afterwards.

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