get_active_task_contexts

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

The description mentions it lists 'active' contexts and clarifies it returns task TYPES not instances, implying a read-only operation. However, without annotations, it doesn't explicitly state it's read-only or disclose other behaviors like ordering or filtering, leaving minor gaps.

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 concise with three sentences: a starter command, the tool's function, and actionable next steps. No wasted words, each sentence adds value.

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 zero parameters and an output schema, the description covers the tool's purpose, output distinction, and usage workflow completely, enabling an AI agent to use it effectively.

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?

There are 0 parameters, so the schema provides full coverage. The description adds no parameter information (none needed), but it adds value by clarifying the output semantics (types vs instances), earning the baseline score of 4.

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 tool lists active task contexts (reusable task TYPES, not task instances), with a specific verb and resource, and distinguishes it from task instances and sibling tools by providing next steps.

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 'Start here for every task' and provides clear decision points: if context matches, use get_artifacts_for_task_context; if not, use create_task_context, guiding the agent on when to use this tool versus alternatives.

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