set_current_directory

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

With no annotations, the description must fully disclose behavior, but it only states the action. It omits critical traits: effect of invalid paths, scope (global/session), persistence, and side effects on other tools. This is a significant gap.

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 one short sentence, which is concise but lacks necessary detail. It could be expanded slightly to include key behavioral context without losing brevity. It earns a middle score for being adequately sized but under-informative.

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?

Despite the tool's simplicity and complete schema coverage, the description fails to provide essential context about scope, validation, or consequences. An agent cannot infer safe usage without additional information, leaving completeness insufficient.

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% (path parameter has a description), but the tool description adds no extra meaning beyond repeating the parameter's purpose. Baseline 3 is appropriate as it neither improves nor degrades schema 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?

The description 'Set the current working directory' clearly states the action (Set) and the resource (current working directory). It is distinct from sibling tools like get_current_directory (read) and execute_command (run), making purpose unambiguous.

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 is provided on when to use this tool versus alternatives, such as prerequisites (e.g., path existence) or context. An agent receives no direction on appropriate invocation scenarios.

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