cl_php_selector_get

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

No annotations are provided, so the description carries the full behavioral burden. It clearly says 'Read', implying a non-destructive operation, and scopes the action to a user/plugin. However, it does not mention prerequisites, error behavior, or what happens if CloudLinux is not present, though the sibling note partially covers the platform condition.

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 compact and well-structured: one core sentence, one routing note, and a one-line argument explanation. Every part earns its place and there is no redundant 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?

For a one-parameter read tool with an output schema, the description provides all essential context: what it reads, who it targets, and when to use a different tool. The output schema handles return-value details, so nothing critical is missing.

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 only provides the title 'Username' and type string, and schema description coverage is 0%. The description's 'username: Account' clarifies that it refers to a DirectAdmin account, which adds some semantic meaning. Still, it is minimal and does not add format, domain, or validation details beyond what the schema already implies.

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 uses a specific verb ('Read') and names the exact resource ('CloudLinux PHP Selector for a user (plugin)'). It also distinguishes itself from the related DirectAdmin PHP selector tool, so an agent can tell it apart from domains_set_php without extra investigation.

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?

It explicitly states the condition for choosing the alternative: 'On non-CL boxes use domains_set_php (DirectAdmin PHP selector) instead.' This gives clear routing guidance and prevents misuse on non-CloudLinux systems.

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