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 the full burden. It mentions the tool 'returns the current artifacts' and 'prompts you to create/update/archive as needed', implying it's a read-and-update operation, but it doesn't disclose behavioral traits like whether it's read-only, destructive, requires specific permissions, or has side effects. For a tool with no annotations, this leaves significant gaps in understanding its behavior.

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 and front-loaded: it starts with the key purpose ('Reflection checkpoint'), followed by usage guidelines and behavioral hints in two concise sentences. Every sentence adds value without waste, making it easy to scan and understand quickly.

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 complexity (reflection and artifact management), no annotations, and an output schema exists (which handles return values), the description is fairly complete. It covers purpose, usage context, and hints at behavior, but lacks details on permissions or side effects. With output schema reducing the need to explain returns, it's adequate but could be more thorough for a tool with no annotations.

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 documents both parameters (task_context_id and learnings) with clear descriptions. The description adds no additional meaning beyond what the schema provides, such as explaining how learnings influence artifact updates. With high coverage, the baseline is 3, as the description doesn't compensate but doesn't detract either.

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 states the tool serves as a 'reflection checkpoint' and prompts artifact management, but it's vague about the specific action. It mentions 'returns the current artifacts' and 'prompts you to create/update/archive as needed', which implies a review-and-update process, but lacks a clear verb+resource combination like 'review and manage artifacts'. It distinguishes from siblings by focusing on reflection, but the purpose isn't precisely defined.

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 context for when to use it: 'before declaring a task complete, and after corrections or user feedback'. This gives clear guidance on timing and scenarios. However, it doesn't mention when not to use it or explicitly name alternatives among siblings, such as direct artifact tools like update_artifact or create_artifact, which could be used without reflection.

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