delete_movie_editor

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

Annotations already declare destructiveHint=true and readOnly=false, and the description adds no behavioral detail beyond repeating the DELETE verb. It does not warn that deletion is permanent, what entities are affected, or what authorizations are required.

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 short and front-loads the HTTP verb and endpoint, with no filler. It could be more informative, but none of the wording is wasted.

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 tool, the description lacks the semantic context needed to use it correctly: what a MovieEditor is, what the body should identify, and the effects of the call. The output schema exists, so return format is not the gap; the call semantics are.

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 body schema is an opaque free-form object with no parameter descriptions, so the description must compensate. 'Request payload' plus a pointer to the GET/schema endpoint is minimal and does not tell the agent what fields the editor delete body should contain.

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 states a Delete action on the MovieEditor endpoint and gives the explicit HTTP route, which distinguishes it from other delete tools. However, 'MovieEditor' is never explained, so it is unclear whether this bulk-deletes movies or deletes some editor entity itself.

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?

No guidance is given for when to use this tool versus delete_movie_by_id, delete_moviefile_bulk, or other delete endpoints. The only operational hint is to read the matching GET or /schema endpoint, which is schema discovery, not use-case guidance.

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