TaskFlow MCP

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions that 'A progress table will be displayed' as an outcome, which adds some context. However, it lacks critical details: whether this is a mutation (implied but not stated), what permissions are needed, if tasks are appended or replace existing ones, or error handling for invalid requestIds.

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 three sentences that are front-loaded: the first states the core purpose, the second adds context about task structure, and the third describes an outcome. No wasted words, though it could be slightly more structured for clarity.

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 (2 parameters with nested objects, 0% schema coverage, no annotations, no output schema), the description is incomplete. It lacks details on return values (beyond mentioning a progress table), error conditions, side effects, or how this tool fits into the broader workflow with sibling tools.

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 mentions 'tasks can include subtasks and dependencies', which clarifies the structure of the 'tasks' array parameter beyond the schema. However, it doesn't explain 'requestId' (e.g., format or source) or provide examples, leaving gaps in parameter understanding.

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 new tasks') and target resource ('to an existing request'), making the purpose evident. However, it doesn't explicitly differentiate this from similar sibling tools like 'add_subtasks' or 'update_task', which would be needed for a perfect score.

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 mentions 'extending a request with additional tasks' but provides no explicit guidance on when to use this tool versus alternatives like 'add_subtasks' (for adding subtasks to existing tasks) or 'update_task' (for modifying existing tasks). No prerequisites or exclusions are stated.

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