Create Document from FTP

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

The description indicates a write operation ('Ingest'), which aligns with annotations (readOnlyHint=false, destructiveHint=false). However, it does not disclose important behaviors like duplicate handling (despite a parameter for it) or what happens to the FTP source after ingestion. The annotations provide some safety cues, but the description adds minimal behavioral context.

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 a single sentence of 9 words, which is very concise. However, it may be slightly under-specified, but it contains no redundant words.

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 tool with 5 parameters and no output schema, the description is minimal. It does not explain the FTP ingestion process, any prerequisites (e.g., file existence on FTP), or what the tool returns. More context would be beneficial for an agent to properly select and use this tool.

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?

All parameters have descriptions in the schema (100% coverage), so the baseline is 3. The description does not add any extra meaning beyond the schema; it merely states the overall action. No parameter-specific guidance is given.

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 explicitly states the verb 'Ingest' and the resource 'a document into a collection from an FTP source', making the purpose clear. It distinguishes itself from siblings like 'create_doc_from_pdf' by specifying the FTP source.

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 on when to use this tool versus alternatives (e.g., other create_doc_from_* tools). There is no mention of prerequisites, such as having configured FTP access or the context needed to perform the ingestion.

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