post_fs_cp

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

The description offers no behavioral information aside from error codes. There are no annotations, so the description carries full burden, which it fails to meet.

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 consists solely of a long, unstructured list of error codes. It is not concise and does not front-load the tool's purpose.

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?

The description is extremely incomplete for a complex operation like a filesystem copy. No information about input, output, behavior, or prerequisites is provided.

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 params, 100% coverage). The description adds a list of error codes but does not explain any parameter meaning or usage, which is irrelevant here. Baseline 3 is reduced due to complete lack of useful parameter context.

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 does not state what the tool does; it only lists error codes. The name 'post_fs_cp' suggests a filesystem copy, but the description fails to confirm this.

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 post_fs_mv or post_fs_rename.

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