cache_delete_file

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description is not the sole carrier of the safety profile. It nonetheless adds information annotations cannot express: the deletion is queued for the scheduler and the tool cannot confirm execution, which changes how an agent should verify results. It stops short of stating permissions or whether a queued delete can be cancelled.

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?

Three short sentences, front-loaded with the action, then the alternative, then the async caveat. No filler and every clause carries decision-relevant content.

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 4-parameter destructive tool with full schema coverage, no output schema, and existing destructive annotations, the description covers the remaining gaps an agent needs: sibling routing, regeneration semantics, and the fire-and-forget execution model.

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 100%, including per-field guidance pointing back to cache_list and the note that 'service' can be omitted for global. The description adds nothing about parameters beyond the schema, so baseline 3 is appropriate.

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+resource with explicit cardinality: 'Delete one job cache file.' The word 'one' plus the sibling reference 'cache_delete_bulk' lets an agent distinguish this from the bulk variant without opening either 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?

Directly names the alternative and the condition that selects it ('Use cache_delete_bulk for several'), and adds a decision-relevant fact ('jobs_run regenerates it') that tells the agent the deletion is not catastrophic. Both when-to-use and when-to-use-something-else are covered.

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