ecp_php_uninstall

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly warns that uninstalling breaks apps still configured to use the version, and discloses that the tool cannot show uninstall output, directing the agent to verify via ecp_php_installed_versions. This is valuable behavioral context beyond the schema.

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?

Three short sentences with no wasted words. The core action is front-loaded, the critical warning comes second, and the verification instruction is last. Every sentence earns its place.

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 destructive uninstall tool with no output schema and no annotations, the description covers the key operational facts: what it does, the risk, and how to verify success. It doesn't explain the version parameter format or whether confirmation is required, but the schema's const true on confirm makes that self-evident. The missing version format detail is a minor gap.

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. It mentions 'a PHP version' but does not explain the 'version' parameter format or the 'confirm' parameter's role. The schema shows 'confirm' is a const true boolean, which is self-explanatory, but the description adds no detail about what version string looks like. Baseline 3 is appropriate since the schema is minimal and the description adds only partial context.

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 ('Uninstall') and resource ('a PHP version'), and immediately distinguishes itself from related PHP tools by noting it breaks apps still using that version. It is clearly differentiated from siblings like ecp_php_install and ecp_php_installed_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 clearly implies when to use it (when you want to remove a PHP version) and warns about the consequence (breaks apps still configured to use it). It doesn't explicitly name alternatives like ecp_php_installed_versions for checking versions, but it does reference checking afterward, which provides practical usage context.

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