action_add_milvus

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

No annotations are provided, so the description carries the behavioral burden. It clearly states what the tool does (adds a Milvus connection) and what becomes available (ctx.MILVUS), but it does not disclose side effects such as whether an existing ctx.MILVUS is overwritten, whether the endpoint must already exist, or any additional configuration or permission requirements.

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?

Two short sentences deliver the core purpose and the resulting context variable. Every word earns its place, and the key information is front-loaded.

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 single-parameter tool, the description is largely adequate, but it omits important operational context: whether the endpoint must already exist, how connection credentials are supplied, and whether calling this tool is idempotent or replaces an existing Milvus connection. Given the sibling context includes action_new and auth_setup, those prerequisites should have been mentioned.

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 100% description coverage for the only parameter `endpoint`, including format and examples. The description adds no extra parameter-level detail, but with full schema coverage this is acceptable baseline.

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 uses a specific action ('Add') with a concrete resource ('Milvus vector DB connection') and a clear target ('to an endpoint's context'). It also names the resulting context variable ('Provides ctx.MILVUS'), making it easy to distinguish from the sibling action_add_* tools.

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 through the name and target: use this when you need to attach a Milvus vector DB to an endpoint's context. However, it does not explicitly contrast with sibling tools like action_add_postgresql or action_add_redis, nor does it state any prerequisites such as the endpoint already existing.

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