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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is covered. The description adds genuinely new behavior beyond that: the deletion is permanent including the underlying bytes, and there is a dependency guard whose refusal message identifies the blocking resource — useful for interpreting failures. No auth or rate-limit context is given.

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?

Two short sentences, zero filler, and the irreversible nature is front-loaded before the refusal condition. Every clause earns its place.

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?

An output schema exists, so return-value detail is unnecessary, and the description covers the two things an agent most needs for a destructive call: permanence and the dependency guard. Only the absence of any guidance on how to clear the blocking dependency keeps it from a 5.

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% and the description never mentions upload_id, so it adds no parameter meaning. With only one required parameter whose name is self-explanatory and whose uuid format is declared in the schema, the invocation is still unambiguous, which keeps this at the minimum-viable level rather than a severe 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?

States a specific verb and resource ("Permanently delete an upload") and adds scope ("and its bytes"). The resource name cleanly separates it from the many sibling deleters (delete_generation, delete_subject, delete_recipe, delete_storyboard), so an agent can route to it without opening the 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?

Gives an explicit precondition for failure — it is "refused while something still uses it — a scene, a Subject, a composition" — which tells the agent when this call will not work and what the blocker looks like. It stops short of naming an alternative route (e.g., detach the scene or Subject first), so it is clear context without explicit alternatives.

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