store-knowledge-bulk

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

With no annotations, the description carries the full burden. It discloses key behaviors: items are 'automatically embedded' and 'stored with a unique ID', plus the storage target (Qdrant). It does not cover error handling or idempotency, but the stated behaviors are meaningful and beyond what the schema provides.

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 sentences, no wasted words. The first sentence states the core purpose, the second adds efficiency context and behavioral detail. All information earns its place.

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 description covers the main usage scenario, efficiency over alternatives, and key behaviors. An output schema exists, so return values need not be described. It lacks details on failure modes or limits, but for a bulk store operation this is largely sufficient.

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?

Schema description coverage is 100%, so the schema documents both items and collection_name. The description adds minimal parameter-specific meaning beyond mentioning 'items' implicitly; it does not explain collection_name, but the schema already covers it adequately.

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 states 'Store multiple pieces of information or knowledge into the long-term knowledge base (Qdrant) at once' – a specific verb and resource with clear bulk scope. It also differentiates from the sibling store-knowledge by noting it is more efficient than calling store-knowledge multiple times.

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 explicitly mentions an alternative ('more efficient than calling store-knowledge multiple times'), which implies use for batched storage. However, it does not explicitly state when NOT to use it (e.g., for a single item use store-knowledge) or other exclusions.

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