delete_folder

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

Beyond the destructiveHint annotation (already indicating destructive behavior), the description adds two critical behavioral traits: the folder is deleted recursively by default, and the operation requires a specific insecure feature to be enabled. These details help the agent understand preconditions and default behavior.

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, front-loaded with the main action, no extraneous text. Every sentence adds value: the first states the action and default behavior, the second states a necessary precondition.

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 description adequately covers purpose, prerequisite, and default behavior for a simple delete operation with two well-documented parameters. It does not mention the return value (e.g., success indication), but no output schema exists, so this is a minor gap for complete agent usage.

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 100% for both parameters, so the baseline is 3. The description reiterates the recursive default but does not add additional semantic meaning beyond what the schema already provides for either parameter.

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 clearly states the verb 'Delete', the resource 'folder', and specifies the scope 'on the machine running the driver'. It also notes the recursive default behavior, which distinguishes it from delete_file, a sibling tool that deletes a single file.

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 explicitly states the prerequisite that the 'modify_fs' insecure feature must be enabled on the Appium server, providing clear usage context. However, it does not explicitly contrast with alternatives or state when not to use this tool, though the sibling list includes delete_file which hints at the distinction.

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