Download a file from the FTP site

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuinely useful non-annotation behavior: binary/.gz files come back base64-encoded while .csv text is returned as-is. It omits rate limits or file-size caveats, keeping it below 5.

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?

Three short sentences, front-loaded with the action, then the path convention, then the return-encoding behavior. No filler.

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?

No output schema exists, so the description appropriately explains what is returned (raw text, base64 for binary). With one fully documented parameter and annotations covering safety, an agent has everything needed to call it correctly.

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 single parameter already carries a description and example, so baseline is 3. The description echoes examples and the relative-path idea but also slightly conflicts with the schema ('relative to the FTP root' vs 'relative to the scores root'), which may cause minor confusion.

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?

States a specific verb+resource: 'Download the raw text content of a file from the PGS Catalog FTP site.' The sibling set is dominated by list_* and search_* tools, so a download-by-path tool is clearly differentiated without ambiguity.

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?

Gives concrete path examples and the relative-path convention, which tells an agent how to invoke it after obtaining a path from the list_* siblings. It does not explicitly state exclusions or when to prefer an API-based sibling (e.g., get_score) over the FTP route, so not a full 5.

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