post_fs_mkdir

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

Without annotations, the description bears full responsibility for disclosing behavior. It only lists error codes without explaining their significance or any side effects (e.g., whether mkdir is destructive, requires specific permissions, or returns a result).

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 line of error codes, which is not concise in a helpful way. It wastes space without conveying the tool's core function or usage, making it inefficient for an AI agent.

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 complexity (file system operation) and lack of output schema or annotations, the description is severely incomplete. It fails to explain what the tool does, how to use it, or what to expect, which is essential for correct invocation.

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 no parameters (0 required, 0 optional, 100% coverage). The description fails to add any meaning beyond the schema; listing error codes is irrelevant to parameter semantics and provides no help.

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 only lists error codes and does not state what the tool does. The name 'post_fs_mkdir' suggests creating a directory, but the description fails to confirm this, leaving the purpose entirely unclear.

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 like get_fs_ls_path or post_fs_rm. There is no mention of context, prerequisites, or exclusion criteria.

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