reset_upload_dir_api_v1_retrieval_reset_uploads_post

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

With no annotations, the description bears full responsibility for disclosing behavioral traits. 'Reset Upload Dir' does not explain what side effects occur (e.g., file deletion, irreversible changes), required permissions, or operational constraints. This is dangerously vague for a potentially destructive operation.

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 extremely short (3 words), but this is not conciseness; it is under-specification. A good description balances brevity with completeness. Here, every sentence is missing, and the description fails to provide necessary context.

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?

Given the lack of annotations and parameters, the description should compensate by explaining what the tool does and its impact. The output schema exists but the description does not reference return values. The tool likely has significant side effects, yet no context is provided.

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 input schema has zero parameters, so schema description coverage is 100%. The description adds no additional meaning beyond the schema. Baseline 3 is appropriate since there is nothing to add, but the description could still clarify that no parameters are needed.

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 'Reset Upload Dir' is essentially a tautology of the tool name. It indicates the tool resets the upload directory but fails to specify what 'reset' entails (e.g., delete all files, clear configuration). It also does not distinguish itself from sibling reset tools like 'reset_vector_db' or 'reset_knowledge_by_id'.

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?

The description provides no guidance on when to use this tool versus alternatives. There are no prerequisites, use cases, or exclusions mentioned. The agent has no information about whether this tool is suitable for a given scenario.

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