ecp_php_set_ini

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

With no annotations, the description is the only safety signal. It usefully discloses that this is a destructive overwrite and warns that malformed content can break all apps on that PHP version. However, it does not mention whether the operation makes a backup, validates the ini syntax, or requires a restart.

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?

Two sentences with no filler. The primary action and the most important risk are communicated immediately, which is appropriately front-loaded for a destructive operation.

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 three-parameter, high-impact mutation without annotations or an output schema, the description is too thin. It covers the key risk warning but omits crucial operational details such as how version should be specified and what 'file_content' must contain, leaving an agent under-informed before invoking a destructive action.

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 needs to compensate. It only hints that file_content is the malformed content being written and that the operation is version-specific, but it does not explain version formats, that file_content replaces the entire file, or how confirm must be supplied.

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 states a specific verb ('Overwrite php.ini') and a resource ('php.ini for a PHP version'), which clearly distinguishes it from siblings like ecp_php_get_ini and ecp_php_installed_versions. It avoids tautology and tells an agent exactly what action is being performed.

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?

There is no explicit guidance about when to use this tool versus alternatives such as ecp_php_get_ini or ecp_php_install. The warning 'Can break every app using that version if malformed' implies caution but does not help an agent select among PHP-related tools.

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