change_directory

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

No annotations are provided, so the description carries the full burden. It only states the function but does not disclose error behavior (e.g., invalid path), effects on session, or any side effects. Minimal transparency.

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 concise with no wasted words. It front-loads the verb 'Muda'. While brevity is good, it could benefit from a slightly more structured format (e.g., separate sentence for clarification).

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 simplicity (1 param) and presence of an output schema, the description need not detail return values. However, it lacks behavioral completeness for a mutable tool (no error or confirmation info), and the language mismatch (Portuguese description with English tool name) may hinder comprehension.

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 description adds the key detail that the path can be relative or absolute, which goes beyond the schema's type-only specification. However, it omits formatting examples, allowed characters, or default behavior, leaving gaps.

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 states the tool changes the session's working directory, specifying it can be relative to the current directory or absolute. This distinguishes it from sibling tools like get_working_directory (read-only) and list_directory (listing contents).

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 for changing directory but provides no explicit guidance on when to use versus alternatives, nor any exclusions or prerequisites. It relies on tool name and context for inference.

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