maestro_list_tasks

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

With no annotations provided, the description carries the full burden. It discloses that the tool lists tasks owned by the authenticated user, which implies a read-only operation, but it does not mention sorting order, pagination, or other behavioral details. The name 'list_tasks' and the description convey the core behavior, but additional context would improve transparency.

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, clear sentence with no redundant information. It is front-loaded with the main action and resource, making it easy to parse.

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?

Given that there is an output schema and the tool is a straightforward list operation, the description is complete enough for basic understanding. It lacks some context like sorting order or use-case hints, but the simplicity of the tool does not require much more. The schema fills in parameter details.

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 input schema covers all three parameters with descriptions (limit, created_at_max, created_at_min), so the schema already provides parameter semantics. The description adds no extra meaning beyond what the schema documents, aligning with the baseline of 3 for high schema coverage.

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 clearly states the action ('List') and the resource ('recent Maestro tasks owned by the authenticated user'). It effectively distinguishes itself from sibling tools like maestro_get_task (single task retrieval) and maestro_create_video (creation).

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 for listing tasks but does not explicitly state when to choose this over alternatives or provide exclusion criteria. It says 'recent' and 'owned by the authenticated user,' which gives some context but no direct comparison to other tools.

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