bulk-delete-media

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

No annotations are provided, so the description must disclose behavior. It only says 'delete' without mentioning that deletion is permanent, that files may bypass the trash (since force defaults to true), or that the operation is irreversible. The schema hints at trash behavior with 'bypass trash', but the description itself lacks this critical context.

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 a single, clear sentence that immediately conveys the action and scope. There is no filler or redundant information, making it highly concise and well-structured.

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 bulk operation, the description is too sparse. It fails to mention the permanent nature of the deletion, the role of the 'force' parameter, or any undo/confirmation mechanism, making it incomplete for safe tool invocation. The lack of an output schema and annotations increases the need for a richer description.

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 input schema has 100% coverage, fully describing the 'mediaIds' array and the 'force' boolean. The description does not add additional meaning about parameter interactions or formatting, so it meets the baseline of 3 for schema-covered parameters.

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?

The description clearly states the verb 'delete', the resource 'media files', and the scope 'multiple at once', which distinguishes it from the sibling tool 'delete-media' for single-file deletion. This is a specific and unambiguous purpose.

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 bulk usage via 'multiple media files at once', but it does not explicitly contrast with the singular 'delete-media' tool or mention prerequisites such as authentication. There is no clear guidance on when to use this vs alternatives beyond the name.

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