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

Annotations already declare destructiveHint=true and readOnlyHint=false, covering the safety profile. The description adds the nuance of 'one or more' files but does not disclose permanence, trash behavior, or side effects on printer assignments. With annotations present, the added context is minimal.

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, efficient sentence with no fluff, front-loading the action. Every word earns its place for a simple tool.

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?

As a destructive operation with one parameter and no output schema, the description should explain return behavior, irreversibility, or effects on related entities (e.g., files referenced by print jobs). It omits these, leaving significant gaps for an agent to reason about.

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 0% with a single string parameter 'file' having no description. The phrase 'one or more' is ambiguous given a single string parameter—it could imply multiple invocations, a list, or a path pattern. The description does not clarify the expected format (e.g., path vs ID), failing to compensate for the schema's gap.

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?

'Delete one or more files.' uses a specific verb and resource, clearly distinguishing it from siblings like delete_folder, move_file, and update_file. The scope ('one or more') adds clarity.

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 (when you need to delete files) but does not explicitly state when to use it versus alternatives or mention exclusions. The sibling names make the context clear, but no direct guidance is provided.

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