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

No annotations exist, so the description carries the full burden and meets it: it warns that deletion is destructive and irreversible, explains recursive removal, describes the deleted/failed return shape, defines force semantics, and spells out the camera/media refusal behavior. This is exactly the behavioral context an agent needs before invoking a destructive tool.

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?

All sentences are substantive and the core action is front-loaded; the media-refusal explanation is verbose but justified because it encodes a subtle failure mode. Could be tightened in phrasing, but no filler.

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?

With no output schema, the description compensates by documenting the return contract (deleted/failed), error-accumulation behavior, and protected paths. For a destructive file tool this is complete enough for an agent to call and interpret results 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 coverage is 100%, so the baseline is 3; the description reinforces bundleId semantics by referencing ios_file_list and clarifies force's behavior, but it does not add much beyond the schema descriptions. It does not contradict the schema.

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?

States exactly what it does—delete a file or directory tree on an iOS device—and adds the key distinction that directories are removed recursively. This separates it clearly from ios_file_list/copy/move/stat and the generic device_file_delete.

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?

Provides a clear use case (clearing an app's cached state between test runs) and ties bundle directory selection to ios_file_list, so an agent knows the same root-selection logic applies. It does not explicitly enumerate alternative tools, but the destructive/refusal warnings plus usual-use context are enough.

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