engine_php_remove

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

No annotations are provided, so the description carries the full burden. It clearly discloses the destructive nature of the operation and goes further by revealing the cascading side effect: for module paths, the .json and view folders in template sets are also deleted. This is valuable behavioral context beyond the parameter 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?

Two short sentences with no filler. The primary action is front-loaded, and the important side-effect condition follows immediately. Every word contributes to the agent's understanding.

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 one-parameter destructive tool with no output schema, the description is largely sufficient: what is deleted, how the path is used, and which additional files are affected. The only minor gap is that 'the .json' is slightly informal and could be clearer about its exact naming/location.

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 provides only a bare 'path' string with 0% description coverage, so the description must add meaning. It explains that path refers to the PHP file to delete and gives the concrete module pattern units/<name>.php that triggers additional cleanup. This meaningfully compensates for the lack of schema documentation.

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?

Description states a specific verb (Delete) and resource (php file by path), making the tool's scope immediately clear. It also distinguishes from sibling remove tools like engine_html_remove or engine_static_remove by being php-specific. The module caveat adds useful specificity rather than confusion.

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 for deleting PHP files and identifies the triggering pattern for module cleanup. However, it does not explicitly state when not to use it or point to alternatives among the many sibling remove tools. An agent must infer the boundary from the tool name and description.

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