Add Documents

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

Annotations already state readOnlyHint=false, destructiveHint=false, idempotentHint=false, so the description is not contradicting anything, but it also adds nothing beyond them. The two most consequential behaviors — what the non-idempotent overwrite flag does to existing collection contents, and what the confirm parameter gates (a safety confirmation for a write) — are never mentioned, and the description does not mention that ingestion can be scoped to the administrator-configured root via include_configured_directory.

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?

It is short, but the second sentence ("Manage collection management operations") earns nothing — it restates the parenthetical and actively misdirects toward collection management. Briefness here is under-specification rather than economy.

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 7-parameter non-idempotent write tool with an output schema, the description should at minimum explain the ingestion sources (paths vs inline contents vs configured directory) and the overwrite/confirm safety semantics. Since an output schema exists it needn't cover returns, but the mutation semantics gap is significant.

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 description coverage is 100%, so the schema already documents all 7 parameters, including the useful note that document_paths are relative paths beneath the configured document root. The description contributes zero additional parameter meaning, which lands at the baseline for high coverage.

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?

"Add documents" names a verb and resource, so the core action is guessable, but the follow-on "Manage collection management operations" muddies it — it describes collection management rather than document ingestion and does not say what kind of documents or where they land. No sibling distinction is offered, though none of the listed siblings appear to ingest documents.

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?

There is no guidance on when to use this versus other approaches, no mention of prerequisites (does the collection need to exist first, per vector_create_collection?), and no explanation of when to choose document_paths vs document_contents or when to set overwrite/confirm. The agent is left to infer everything from parameter names.

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