ftp_list

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

No annotations are present, and the description omits critical behavioral details such as whether the operation is read-only, the format of the returned data, or any side effects. The pagination advice is helpful but insufficient.

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?

Two sentences with no extra words. The action is front-loaded, and the guidance on pagination is directly relevant.

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?

With no output schema, the description should indicate what the list returns (e.g., an array of file names). This is a key omission for an agent to use the tool's output effectively.

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 coverage is 100%, and the description adds value beyond the schema by explaining the purpose of pagination (avoiding context overflow), reinforcing the use of limit and offset.

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 verb 'List' and the resource 'files and directories in a remote path', distinguishing it from sibling tools like ftp_list_transactions or ftp_get_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?

It provides explicit guidance on using limit and offset for pagination to avoid context overflow, but does not mention when not to use this tool or point to alternatives like ftp_tree for recursive listing.

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