ftp_connect

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

The only disclosed behavior is the fallback to FTP_HOST, FTP_USER, and FTP_PASSWORD environment variables if the tool is not called. It does not describe what happens on success (e.g., whether a global connection is created), what occurs if already connected, error handling, or security implications of using plain FTP vs FTPS. With no annotations, the description carries the full burden but only covers a minor aspect.

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 extremely concise—two short sentences—and immediately conveys the primary action. It contains no filler or redundant information with the schema.

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?

For a connection tool with no output schema, the description omits critical contextual details: what the connection state is, how it affects subsequent sibling tools, whether it opens a persistent connection, what permissions or prerequisites exist (e.g., network access), and what happens if the connection fails. The env var fallback is useful but not sufficient for an agent to use this tool reliably.

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 already provides descriptions for all five parameters (100% coverage). The description adds value by explaining that host, user, and password can be overridden by environment variables if the tool is not called, which supplements the parameter meanings beyond the schema's static descriptions.

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 verb and resource: 'Connect to an FTP server.' It is distinct from its siblings, which are all FTP operations that require an established connection. This makes it the obvious connection initializer.

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?

Usage is implied: one should call this before using other FTP tools, and if not called, environment variables will be used. However, there is no explicit 'when to use' or 'when not to use' guidance, nor mention of alternatives like using environment variables directly.

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