jio_delete_files

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

With no annotations provided, the description carries full responsibility. It discloses that the operation moves files to trash (not permanent deletion), the dry_run default, and the explicit requirements for a real delete. This is valuable context beyond the schema fields.

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?

The description is two sentences with no unnecessary words. It front-loads the primary action and immediately conveys the safety defaults, making it highly efficient.

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 simple 3-parameter tool with no output schema, the description covers the core behavior and parameter semantics well. It explains the soft-delete nature and the flags needed for actual deletion, but omits details like response or reversibility, which are less critical here.

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%, but the description compensates by explaining all three parameters: ids (objectKey ids), dry_run (default true), and confirm (required for real delete). It adds practical meaning to each parameter, though it does not detail id format or edge cases.

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 action 'Move files to trash by objectKey ids' with a specific verb and resource. It distinguishes itself from sibling tools like jio_delete_album and jio_delete_duplicates by focusing on files and the objectKey identifier.

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 explains the safety mechanism (dry_run defaults to true, real delete requires dry_run=false and confirm=true) but gives no explicit guidance on when to use this tool versus alternatives. There are no scenarios or exclusions mentioned, which is a gap given the many sibling delete tools.

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