TaskFlow MCP

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key behaviors: it's a mutation tool (implied by 'Mark... as done'), triggers a progress table display, and has workflow constraints (don't proceed until approval). However, it doesn't mention potential side effects like task status changes or error conditions.

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 and front-loaded with the core purpose. The three sentences each serve distinct purposes: action definition, parameter guidance, and workflow rules. It could be slightly more concise by combining some workflow details.

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 mutation nature, 3 parameters with 0% schema coverage, and no output schema, the description does a good job covering purpose, usage, and basic behavior. It lacks details on error handling, response format, and exact effects on the task, but provides sufficient context for basic use.

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 explains that 'requestId' and 'taskId' are required to identify the task, and 'completedDetails' is optional for adding notes. This adds meaningful context beyond the bare schema, though it doesn't detail parameter formats or constraints.

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 specific action ('Mark a given task as done') and resource ('task'), distinguishing it from siblings like 'mark_subtask_done' (for subtasks) and 'update_task' (for general updates). It precisely defines the tool's function as completing a task with optional details.

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 guidance on when to use this tool ('after you've completed it') and when not to proceed ('DO NOT proceed to 'get_next_task' again until the user has explicitly approved this completed task using 'approve_task_completion''). It clearly distinguishes this from the workflow of getting and approving tasks.

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