embed_multilingual

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

With no annotations provided, the description carries the full burden. It does disclose the output dimensionality (1024) and model (BAAI BGE-Large), which is useful. However, it omits other behavioral traits such as output format, handling of arrays, any rate limits, or normalization behavior. The disclosure is partial.

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, concise sentence that is front-loaded with the action. It contains no redundant words or filler, making it highly efficient and easy to process.

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?

The tool is simple with one parameter and no output schema. The description covers the core purpose, dimensionality, and model, which is largely sufficient for selection. It could mention the return type explicitly, but that is reasonably implied by 'embeddings'. Overall, it is adequately complete for its complexity.

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 schema has 0% description coverage, so the description must compensate. It adds meaning to the 'text' parameter by specifying it is multilingual and long text, which provides some semantic context. However, it does not explain that the parameter can be a single string or an array, nor does it give format details beyond the schema's type information.

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 tool's function: generating 1024-dimensional dense vector embeddings for multilingual and long text using the BAAI BGE-Large model. This specifies the verb, resource, and key differentiators from siblings like embed_text, making the purpose explicit and distinct.

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 implies usage for multilingual and long text, giving some context on when to use it. However, it does not explicitly state when not to use this tool or reference alternatives (e.g., embed_text for simpler cases). The guidance is implied rather than clearly stated.

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