shell_set_default_workdir

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

No annotations are provided, so the description alone must disclose the tool's behavioral traits. It only says 'set default working directory' without explaining persistence, session scope, how to reset, or side effects on subsequent commands. The description does not contradict annotations (none exist) but fails to expose key behavioral facts.

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, straightforward sentence that states the action and object clearly without unnecessary words. It front-loads the primary function. It is appropriately sized for a simple setter tool, though it could be expanded with usage context without losing conciseness.

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 simplicity (one parameter, no output schema), the description is minimal but incomplete: it does not state the scope of the setting (e.g., whether it applies to all subsequent executions), how it interacts with shell_execute, or any reset mechanism. The schema describes the parameter but the tool's broader execution context is left to inference.

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 the sole working_directory parameter is already documented in the schema. The description adds little beyond restating that it sets the directory, which is essentially the parameter's purpose. Hence a baseline 3 is appropriate; the description provides no extra parameter details.

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 states a specific action ('Set') and a clear resource ('default working directory for command execution'), which distinguishes it from execution and observation tools among the siblings. It is not a tautology and gives enough to understand the core purpose, though it doesn't explicitly name alternatives.

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 given on when to use this tool vs. shell_execute or terminal_operate. The phrase 'for command execution' hints that it is a prerequisite, but there is no explicit statement of when to use or when not to use it, nor any alternative naming.

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