minimax_get_task

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

With no annotations provided, the description carries the behavioral disclosure burden. It explains task states (pending, completed, failed) and what the return contains, adding context about status tracking. It doesn't explicitly state it's read-only, but as a query tool this is implied and sufficient.

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 well-structured with sections for usage, states, and returns, making it easy to scan. It is somewhat longer than the minimum but each section adds value, particularly the task states list. It could be slightly condensed but remains efficient.

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 simple single-parameter query tool with an output schema, the description is thorough. It covers when to use it, what states to expect, and what the response includes. The presence of an output schema means it doesn't need to detail return structure, making this complete.

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 has 100% coverage of the single parameter task_id, including a description of it as the ID returned from generation requests. The tool description itself does not add much beyond the schema, so the baseline of 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?

The description clearly states 'Query the status and result of a video generation task', specifying the exact verb and resource. It distinguishes itself from sibling tools like minimax_get_tasks_batch by focusing on a single task, making its purpose unambiguous.

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 provides explicit 'Use this when' scenarios, such as checking if a generation completed, retrieving video URLs, and getting full details. It gives clear context for when to use this tool, though it doesn't explicitly name alternatives or exclusions.

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