Task Context MCP Server

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

No annotations are provided, so the description carries full burden. It discloses constraints (English only, character limits) and a next step action, which adds useful behavioral context. However, it doesn't cover permissions, error conditions, or what happens if constraints are violated, leaving gaps 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?

Well-structured with clear sections: purpose statement, usage guidance, constraints, and next step. Every sentence adds value with no redundancy. The bullet-point format for constraints enhances readability without wasting space.

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 that there's an output schema (which handles return values), no annotations, and 100% schema coverage, the description provides good context for a creation tool. It covers purpose, usage, constraints, and next steps. The main gap is lack of error handling or permission information, but overall it's reasonably 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?

Schema description coverage is 100%, so the schema already fully documents both parameters. The description adds marginal value by reiterating character limits and English-only constraints, but doesn't provide additional semantic context beyond what's in the schema descriptions.

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 verb 'Create' and resource 'new task context (task type)', specifying it's for when no match exists. It distinguishes from siblings by focusing on categories rather than specific instances, though it doesn't explicitly name alternative tools for different scenarios.

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?

Provides clear context: 'when no match exists' and 'for categories (e.g., "CV analysis for Python dev"), not specific instances'. It also mentions a next step with create_artifact(). However, it doesn't explicitly state when NOT to use this tool or name specific alternative tools from the sibling list.

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