TaskFlow MCP

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

No annotations are provided, so the description carries the full burden. It discloses that this is a write operation ('Add'), mentions the outcome ('A progress table will be displayed showing the updated task with its subtasks'), and explains the relationship between subtasks and tasks ('All subtasks must be completed before a task can be marked as done'). However, it lacks details on permissions, error conditions, or whether this operation is idempotent, which are important for a mutation tool.

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 appropriately sized with four sentences that are front-loaded: the first sentence states the purpose and parameters, the second explains subtasks, the third adds context about task completion, and the fourth describes the output. There's minimal waste, though the second sentence could be slightly more concise.

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 the complexity (a mutation tool with 3 parameters, no annotations, and no output schema), the description is moderately complete. It covers the purpose, parameters at a high level, behavioral context (subtask-task relationship and output display), but lacks details on parameter formats, error handling, and exact return values. For a tool that modifies data without annotations, this leaves gaps in operational understanding.

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%, so the description must compensate. It lists the required parameters ('requestId', 'taskId', and 'subtasks array') and explains that subtasks have 'title' and 'description' fields, which adds meaning beyond the schema. However, it doesn't clarify what 'requestId' and 'taskId' represent (e.g., their format or how to obtain them), leaving key parameters partially undocumented.

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 ('Add subtasks') and target resource ('to an existing task'), making the purpose immediately understandable. It distinguishes this tool from siblings like 'add_tasks_to_request' (which adds tasks to requests) and 'add_dependency' (which adds dependencies between tasks). However, it doesn't specify what type of tasks/subtasks these are (e.g., project management tasks), leaving some context implicit.

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 context by stating 'Add subtasks to an existing task' and mentioning that 'All subtasks must be completed before a task can be marked as done,' which suggests this should be used when breaking down tasks into smaller units. However, it doesn't explicitly state when to use this versus alternatives like 'plan_task' (which might also involve subtask planning) or 'update_task' (which might modify existing subtasks), nor does it mention prerequisites like needing an existing task ID.

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