reindex_knowledge_base_metadata_embeddings_api_v1_knowle

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

Discloses that it loops through all knowledge bases, makes N external embedding API calls, and intentionally avoids holding a session to prevent connection pool exhaustion. This covers key behavioral aspects beyond the absence of annotations.

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 very concise, front-loads the purpose, and includes necessary technical context in a note. Every sentence is valuable without redundancy.

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 no parameters and the presence of an output schema, the description covers the tool's purpose, admin requirement, and important performance implications thoroughly.

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?

No parameters exist, so schema coverage is 100%. The description does not need to add parameter information; a baseline score of 4 is appropriate.

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 'Batch embed all existing knowledge bases' with a specific verb and resource, distinguishing it from sibling tools like reindex_knowledge_files by focusing on metadata embeddings.

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?

Explicitly restricts to 'Admin only', providing a clear usage constraint. While it doesn't mention alternatives, this is sufficient for a batch operation tool.

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