s3_delete_objects

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

The annotations already mark this as destructive (destructiveHint: true), but the description does not elaborate on permanence, potential failures (e.g., governance restrictions), or the need for confirmation. The bypassGovernance parameter is not mentioned in the description, leaving the agent unaware of conditions that may affect the operation.

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 concise sentence, directly stating the purpose without fluff. It includes the key constraint ('up to 1000 objects') efficiently. No unnecessary words.

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?

Given the absence of an output schema, the description does not explain return formats, but it adequately covers the tool's core purpose and key operational bound. It does not mention error handling or prerequisites, but these are not critical for the agent's initial selection. The description is sufficiently complete for a simple deletion operation.

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 schema description covers 100% of parameters, so the baseline is 3. The description adds no additional semantic detail about parameters; it only restates the action. No extra value is provided beyond 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?

The description clearly states the action: 'Delete multiple objects from a B2 bucket' with a specific bound ('up to 1000 objects'). It distinguishes itself from singular deletion (s3_delete_object) by emphasizing multiple objects and the concurrency bound.

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 usage for bulk deletion ('multiple objects'), but does not explicitly state when to choose this tool over alternatives like s3_delete_object or when not to use it (e.g., for single-object deletion). The concurrency bound is mentioned but not framed as a selection criterion.

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