tool.set

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

No annotations provided, so description must disclose behavior. It states the action but does not mention side effects (e.g., tool change, undo stack), error handling for invalid idname, or dependence on active area_type.

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 sentence), which is concise but sacrifices necessary detail. It lacks structure and front-loads only the basic action, omitting parameter context.

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?

With 3 parameters, no output schema, and no annotations, the description is far from complete. It does not cover return values, behavior for invalid inputs, or the impact of default parameter values.

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 0%, meaning description must explain parameters. It only references 'idname' but does not explain its format, valid values, or the roles of 'mode' and 'area_type'. This fails to add value beyond 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 uses a specific verb 'switch' and resource 'active workspace tool', and mentions the key parameter 'idname'. It clearly distinguishes from sibling tools like 'tool.active' (read) and 'tool.settings' (configure settings).

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?

No guidance on when to use this tool versus alternatives (e.g., tool.active, tool.settings). No prerequisites or restrictions mentioned, which is insufficient for an action that modifies workspace state.

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