get_php_version_for_domain

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

With no annotations provided, the description must convey the behavioral profile. 'Get' clearly implies a read-only, non-mutating operation. However, it does not mention edge cases such as behavior when the domain does not exist or when no PHP version is assigned, but for a simple getter this is adequate.

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 sentence of 11 words, fully front-loaded with the action and resource. Every word earns its place, with zero redundancy.

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 simple one-parameter getter with no output schema, the description adequately specifies the return concept (the PHP version). It lacks details about error behavior or format variations, but these are not essential for a straightforward query tool.

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 has 100% coverage for the only parameter 'domain' with description 'Domain name to check'. The tool description adds minimal extra meaning beyond the schema, so a baseline score of 3 is appropriate given the schema already carries the semantic weight.

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 tool's function with a specific verb ('Get') and resource ('PHP version assigned to a domain'). It distinguishes from sibling tools like set_php_version_for_domain and list_php_versions by focusing on the current assignment for a specific domain.

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 usage (query the current PHP version for a domain) but does not explicitly state when to use this tool versus alternatives like list_php_versions or set_php_version_for_domain. There are no exclusions or when-not-to-use conditions provided.

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