Task Context MCP Server

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 behavioral traits: the default filtering behavior ('Defaults to practice/rule/prompt (excludes result)'), the conditional use of include_archived parameter, and the tool's role in workflow sequencing. It doesn't cover all possible behavioral aspects like error conditions or performance characteristics, but provides substantial operational context.

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 perfectly structured and concise. It begins with the core purpose, provides clear usage guidelines in bullet points, and includes important notes without any wasted words. Every sentence serves a specific purpose in guiding the agent's understanding and usage.

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 an output schema exists (so return values are documented elsewhere), no annotations are provided, and the tool has moderate complexity, the description does an excellent job covering operational context. It explains when to call the tool, what it defaults to, and special considerations for archived artifacts. The main gap is lack of explicit differentiation from sibling tools, but otherwise provides comprehensive guidance for proper usage.

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 all parameters thoroughly. The description adds some value by explaining the default behavior for artifact_types ('defaults to all except 'result'') and providing guidance on when to use include_archived, but doesn't add significant semantic meaning beyond what the schema already provides. This meets the baseline expectation.

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 'Load' and resource 'artifacts for a task context', making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'search_artifacts' or 'get_active_task_contexts', which reduces clarity about when to use this specific retrieval method versus alternatives.

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 excellent usage guidance with explicit timing instructions: 'Call this after you select or create a task context and before doing work' and 'Re-call when you start a new phase or need to confirm guidance.' This clearly tells the agent when to invoke this tool versus other operations.

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