cl_php_selector_set

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It signals mutation with 'Set' and mentions confirm, but does not explain what confirm does, whether the change is reversible, what side effects may occur, or if special permissions are required.

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 short and front-loaded, with a clean Args block. It earns its space, though the misleading 'confirm: Required' line prevents a perfect score.

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?

For a mutating tool with no annotations and incomplete parameter semantics, this description leaves too much unsaid: what happens after the version is set, whether confirm affects execution, and when the user should prefer this over cl_php_selector_get. It is minimally functional but not complete.

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%, so the description is the only source of parameter meaning. It usefully defines username and provides concrete version examples like 8.2 and native. However, it states 'confirm: Required' while the schema marks confirm as optional with a default of false, creating a contradiction that undercuts reliability.

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 opens with a clear verb and resource: 'Set CloudLinux PHP Selector version for a user.' This precisely distinguishes the tool as a mutating counterpart to cl_php_selector_get, leaving no ambiguity about what it does.

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 given on when to use this tool versus alternatives such as cl_php_selector_get or other CloudLinux tools. The context is implied by the 'Set' action, but there are no exclusions, prerequisites, or explicit routing cues.

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