Taskwarrior MCP Server

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

Annotations already indicate this is a non-destructive, non-read-only, non-idempotent operation. The description adds valuable context about what gets created (new tasks with specific attributes) and the confirmation message format, though it doesn't mention rate limits, authentication needs, 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?

Well-structured with clear sections (purpose, usage, Args, Returns, Examples) and front-loaded information. The examples are helpful but somewhat lengthy; every sentence earns its place by providing concrete guidance.

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 tool's moderate complexity, 0% schema description coverage, and presence of an output schema, the description provides complete context. It explains what the tool does, how to use parameters, what to expect in return, and includes multiple examples covering common use cases.

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?

With 0% schema description coverage, the description fully compensates by explaining all parameter semantics through examples and the Args/Returns sections. It clarifies what each optional field means (project, priority, due date, tags) and provides concrete usage examples that add meaning beyond the bare schema.

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 ('Create a new task in Taskwarrior') and resource ('task'), distinguishing it from siblings like modify, delete, or list. It explicitly identifies what the tool does beyond just the name.

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 implied usage guidance ('Use this tool to add new tasks') and mentions optional attributes, but doesn't explicitly state when to use this vs alternatives like taskwarrior_modify or taskwarrior_annotate. No clear exclusions or prerequisites are mentioned.

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