workspace_state

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

With no annotations, the description must disclose behavioral traits. It does not mention that actions like 'clear_history' and 'clear_cache' are destructive, nor any permissions or side effects. The read/write nature of each action is implied only through action names.

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 very short (one line) and concise, though it is a simple list without structural hierarchy (e.g., bullet points). It conveys the available actions efficiently for a compact tool.

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 (9 distinct actions), the description only provides action names without explaining their behavior. The schema fills the gap, but the description alone is insufficient for an agent to understand the tool's full capabilities.

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?

The input schema has 100% description coverage, so the baseline is 3. The tool description adds minimal value beyond listing action names; detailed parameter semantics are deferred entirely to the schema.

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 lists sub-actions like 'full sync, snapshot, recent changes' but lacks a clear, single-sentence statement of the tool's overall purpose. It reads as a list rather than a coherent description, leaving ambiguity about the tool's primary function.

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 no guidance on when to use this tool versus its siblings (e.g., manage_sync, query_instances). It does not mention prerequisites, context, or alternative approaches for achieving similar results.

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