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

Annotations already declare destructiveHint=true and idempotentHint=true, yet the description adds substantial context beyond them: irreversibility with no trash on Android, refusal of storage roots with a rationale (path-construction bugs like an empty variable), and error-not-silent-success semantics for non-existent paths. These are exactly the operational traits an agent needs for 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?

Front-loaded with the core action and recursiveness, then layered with the highest-stakes fact (NOT REVERSIBLE), then the guard rails and error semantics. Four sentences, each carrying distinct, non-redundant information.

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-parameter tool with no output schema, the description covers irreversibility, refusal boundaries, and error reporting. There is no output schema to explain and nothing an agent needs to call it safely that is missing.

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 both parameters are documented structurally (baseline 3). The description adds meaning to remotePath beyond the schema's terse 'Absolute path... to delete' by specifying which roots are refused and that non-existent paths error out, giving the agent real constraints on valid values.

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 a specific verb and resource ('Delete a file or directory on the device (recursive)') and explicitly distinguishes itself from its sibling ios_file_delete as the Android counterpart. An agent can identify the tool's function and platform scope without opening the schema.

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?

Clearly positions itself against the ios_file_delete sibling and implies the Android-platform context, but offers no explicit when-not-to-use guidance or alternative tools for edge cases (e.g., a safer move-to-trash path does not exist, which it notes, but no alternative is suggested). Context is clear, exclusions are absent.

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