ms_gui_project_dir

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

The term 'Ensure' is ambiguous—it may imply creating the directory if it doesn't exist, which is a behavioral trait. Without annotations, the description does not clarify whether side effects (e.g., creation) occur, nor does it mention permissions, idempotency, or error conditions. This lack of transparency could lead to misuse.

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 sentence of 14 words, front-loading the key action ('ensure and return'). It is efficient, though the word 'ensure' could be clarified for better scannability.

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 absence of annotations and output schema, the description carries the full burden of explaining the tool's behavior. It omits details about the return value format, whether the directory is created, and any required permissions. For a simple tool, this may be marginally adequate, but it lacks completeness for an AI agent to understand all nuances.

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 zero parameters, so schema description coverage is 100%. According to guidelines, a baseline of 4 is appropriate. The description does not need to add parameter information, and it provides no misleading 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 clearly identifies the tool's purpose: to ensure and return the current MS-MCP session output directory. The verb 'ensure and return' combined with the resource 'directory' provides specific action and object, distinguishing it from sibling tools like ms_gui_state or ms_list_workspace which have different scopes.

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 implies usage when the current session output directory is needed, but does not explicitly state when to use this tool versus alternatives like ms_list_workspace. No exclusions or prerequisites are provided, leaving the agent to infer context.

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