MCP RAG Server

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

With no annotations provided, the description carries full burden. It states the tool 'Clear[s] and refresh[es]' which implies a destructive/replacement operation, but doesn't disclose important behavioral traits like whether this requires admin permissions, how long it takes, if it's asynchronous, what happens during the process, or what the expected outcome is.

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, efficient sentence that communicates the core purpose without any wasted words. It's appropriately sized for a zero-parameter tool and front-loads the essential information.

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 potentially destructive operation with no annotations and no output schema, the description is inadequate. It doesn't explain what 'clear' means (deletion? reset?), what 'refresh' entails, whether this affects search availability during the process, or what confirmation/status is returned.

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 tool has 0 parameters with 100% schema description coverage, so the baseline is 4. The description appropriately doesn't waste space discussing non-existent parameters, though it could theoretically mention that no configuration options are available for this operation.

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 action ('Clear and refresh') and target ('the entire document index'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'ingest_docs' or 'search' that might also interact with the document index in different ways.

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 about when to use this tool versus alternatives like 'ingest_docs' (which might add documents) or 'search' (which queries the index). The description implies this is for maintenance/rebuilding operations but doesn't specify triggers or prerequisites.

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