ck_workspace_agent

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

The description reveals key behaviors: the existence of a primary agent restriction, modes that modify state (register, update, retire), and the notion of ephemeral agents. It adds context beyond annotations, such as the super-agent concept, and does not contradict annotations.

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 a single paragraph that efficiently conveys the modes and constraints. It is reasonably concise but could be improved by using bullet points or shorter sentences for easier scanning.

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 (11 parameters, nested objects, output schema), the description adequately covers the modes and role constraints. It does not explain return values, but an output schema exists. It provides sufficient context for an AI agent to understand the tool's scope.

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 baseline is 3. The description adds value by explaining the mode semantics and role constraints but does not delve into parameter details beyond what schema already provides. The schema already describes each parameter adequately.

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's purpose: managing workspace agent roles with specific modes (register, update, list, health, retire). It identifies the resource (workspace agents) and differentiates from sibling tools by focusing on agent lifecycle management.

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 some usage guidance by explaining when to use each mode (e.g., 'only one primary per workspace') but does not explicitly contrast with alternatives among the many sibling tools. It implies when to use certain modes but lacks explicit when-not-to-use guidance.

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