combell_linux_hostings_php_versions

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is clear. The description adds a little context by specifying that the listing is scoped to a Linux hosting, but it does not disclose additional behaviors such as return format, ordering, or error cases.

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, front-loaded sentence with no filler. Every word contributes to identifying the operation, making it easy for an agent to parse quickly.

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 tool's low complexity, one parameter, and safe read-only annotations, the description is largely sufficient. There is no output schema, so a slight note about what the returned list contains would improve completeness, but the core invocation context is clear.

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 must compensate for the undocumented domain_name parameter. It partially does by saying 'for a Linux hosting,' which links domain_name to the hosting's domain, but it does not explicitly explain the parameter's format or required semantics beyond the schema's required flag.

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 ('List') and a clear resource ('PHP versions available for a Linux hosting'), which makes the tool's read-only purpose immediately obvious. It also distinguishes itself from sibling tools like combell_linux_hostings_set_php_version by emphasizing enumeration rather than modification.

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 implies when to use the tool: when the agent needs to know which PHP versions are available for a Linux hosting. However, it does not explicitly state when not to use it or mention alternatives such as combell_linux_hostings_set_php_version for changing the version.

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