fm_list

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

There are no annotations, so the description carries the transparency burden. It does add a useful behavioral constraint: path must be an absolute path inside the account home. 'List' also implies a read-only operation, but the description does not clarify hidden files, sorting, error behavior, or whether the listing is recursive.

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 and front-loaded: 'List a directory.' followed by a single parameter explanation. There is no filler or redundant content; every sentence adds value.

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 tool is simple and has an output schema, which reduces the need to describe return values. However, the description gives no help distinguishing fm_list from the many related fm_* siblings, and it lacks usage context such as whether this lists only immediate children. It is adequate but has clear gaps.

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 schema gives only the parameter name, type, and default, with 0% description coverage. The description compensates by explaining that path is an absolute path inside the account home, which clarifies that the default '/' means the account home root. Slightly more detail about boundary restrictions would push this to 5.

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's action and resource: 'List a directory.' This is specific and understandable. However, it does not explicitly differentiate fm_list from related siblings like fm_tree, fm_search_files, or fm_disk_usage, so it stops short of a 5.

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 about when to use fm_list versus related file-management tools. The description does not mention alternatives, exclusions, or conditions such as 'use fm_tree for recursive listings.' This is essentially no usage guidance beyond the action itself.

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