uninstall_php_extension

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

No annotations are provided, so the description carries the full behavioral burden, and it says nothing about the destructive nature of an uninstall, required permissions, reversibility, service restarts, or side effects. The word 'Uninstall' implies irreversible mutation but no detail 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?

A single four-word sentence is maximally terse and front-loaded, but here brevity reflects under-specification rather than efficiency; there is no wasted text but also nothing that earns its place beyond the name.

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 two-required-parameter operation with no annotations, no output schema, and zero schema documentation, the description provides none of the context an agent needs to invoke it correctly.

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% and the description does not mention either required parameter. It is unclear what 'id' refers to (a PHP runtime? a website?) or what form the 'extension' string takes, leaving both parameters undocumented.

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 'Uninstall PHP extension' is a verbatim restatement of the tool name uninstall_php_extension, which the rubric classifies as a tautology. It conveys a verb and resource but adds no scope, target, or distinguishing detail beyond the name itself.

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 guidance on when to use this tool versus alternatives such as install_php_extension or list_php_extensions, nor any stated prerequisites. Usage must be inferred entirely from the name.

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