ecp_php_get_ini

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

With no annotations, the description carries the full burden, but it only says 'Get', which suggests a read operation. It does not disclose whether the tool returns the raw file, parsed key/value pairs, or what errors occur for invalid versions. No parent/destination info is given.

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 concise sentence with no redundant words. It front-loads the action and resource, but it could have used the brevity to add a small detail about the return type without violating conciseness.

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?

The tool has no output schema and only one parameter, yet the description does not explain what is actually returned (whole config? specific values?) or any error conditions. An agent would need to guess the response format, making the description incomplete even for a simple getter.

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 lists 'version' as a string with 0% coverage, so the description must compensate, but it only says 'PHP version' without format, valid values, or relation to installed versions. It does not explain which version strings are accepted or where to find them.

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 action 'Get', the resource 'php.ini values', and the scope 'for a PHP version'. It distinguishes the tool from siblings like ecp_php_set_ini (which writes) and ecp_php_installed_versions (which lists versions).

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 provides no guidance on when to use this tool versus alternatives. It does not mention that the version should be one from ecp_php_installed_versions, nor does it contrast with ecp_php_set_ini. Usage context is left entirely to the agent's inference.

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