create_task_context

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

No annotations are provided, so description carries full burden. It discloses constraints and next step but does not discuss idempotency, side effects, or error handling. Basic transparency but lacks depth for a creation 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?

Description is concise: five well-structured lines covering purpose, usage, constraints, and next step. Every sentence adds value with no redundancy.

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?

Tool has output schema so return values need not be explained. Description covers constraints and suggested next step. However, it lacks mention of error cases or failure handling. Given low complexity (2 params), completeness is good but not perfect.

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 coverage is 100% with descriptions for both parameters. Description adds value by stating max char limits (200 for summary, 1000 for description) and 'English only' constraint, which are not in the schema. Effectively enhances 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?

Description clearly states 'Create a new task context (task type) when no match exists' and explicitly differentiates from specific instances with example 'CV analysis for Python dev'. Distinguishes from sibling tools like get_active_task_contexts.

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?

Explicitly says 'when no match exists' and 'Use for categories, not specific instances'. Provides constraints (English only, char limits) and a next step to create guidance with create_artifact(). Clearly guides when and how to use the tool.

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