agent-tool

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

No annotations provided, so description carries full burden. Discloses critical behavioral traits: session reuse mechanics, async operation patterns (returns transfer_id immediately), file size limits, and safety constraints on recursive delete. Could improve by mentioning error handling or rate limiting behaviors.

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?

Seven sentences, each earning its place: purpose, session reuse, operation list, async operations, size limits, overwrite guidance, and safety limits. No redundant or filler text. Well front-loaded with protocol and scope.

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 complex 22-parameter tool with multiple operation modes (sync/async) and no output schema, description adequately covers authentication, available operations, and critical limits. Minor gap: does not describe return value structure or success/failure indicators for operations.

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 has 100% description coverage, establishing baseline of 3. Description references specific parameters ('overwrite=true', 'transfer_id') to illustrate behavior but does not add semantic meaning beyond what schema already provides for the 22 parameters.

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?

Description opens with specific verb+noun ('Transfer files and manage remote filesystems') and protocol ('SFTP'). Explicitly distinguishes from sibling 'ssh' tool by noting session pool reuse while clarifying distinct file operations (upload, download, ls, etc.).

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?

Provides concrete constraints (2GB max file size, 10,000 item recursive delete limit) and configuration hints ('Use overwrite=true'). Mentions relationship to ssh tool for authentication context. Lacks explicit guidance on when to prefer this over siblings 'download' or 'upload' (likely HTTP-based alternatives).

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