codex_app_fs

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

With no annotations, the description must convey behavioral traits. It mentions 'governed' and 'allowlisted roots' but fails to disclose critical details such as authorization requirements, destructive behavior (remove, force overwrites), watch lifecycle semantics, or response formats. This is a significant gap for a mutation-capable tool.

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, front-loaded sentence with no filler or repetition. It is concise and readable, though its brevity sacrifices useful detail.

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?

This tool has 10 parameters, 9 action variants, no output schema, and no annotations. The description provides only a broad overview and lacks essential context about return values, action-specific requirements, filename/path constraints, binary handling, and error behavior. It is far from complete for safe 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?

Schema description coverage is 0%, and the description does not compensate by explaining parameter meanings. It names operation types (read, write, copy) but does not clarify relationships between path, text, sourcePath, destinationPath, watchId, or other parameters. The agent cannot infer semantics beyond the bare schema names.

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 that the tool performs governed filesystem operations (read/write/list/copy/remove/watch) on the app-server filesystem v2 under allowlisted roots. It distinguishes itself from sibling tools by naming the filesystem and operation scope, though it lacks a single verb+resource phrasing.

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 gives context about governance and allowlisted roots but does not specify when to use this tool versus alternatives. No explicit exclusions or sibling comparisons are provided, leaving usage decisions to the agent.

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