The three tools map to clearly distinct actions: creating a video task, fetching a single task's status/outputs, and listing recent tasks. There is no plausible way to confuse create with get or list, and descriptions reinforce the async task_id workflow.

All tools use a uniform maestro_ prefix followed by a consistent verb_noun pattern (create_video, get_task, list_tasks). The convention is predictable and readable throughout.

Three tools is on the lean side but each earns its place in the create-then-poll-via-task_id pattern, so the surface is well-scoped rather than padded. It is slightly thin in that there is no cancellation or asset-management tool.

The core lifecycle is covered: submit a job, monitor it, and enumerate prior jobs with outputs (video, captions, cover). Minor gaps exist around cancelling a running task or deleting/retrieving past assets, which agents cannot do with the current surface.