qdrant-store

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It only states the basic action without mentioning side effects (e.g., overwriting, idempotency, permissions, or error conditions). This is insufficient for a mutation tool.

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 sentence, which is concise, but it is not front-loaded with the essential verb and could be more efficient (e.g., 'Store information for later retrieval'). It is adequate but not exemplary.

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?

With no output schema and no annotations, the description should provide more context about return values, storage behavior, and error handling. The current description is too minimal to fully inform an agent about using this tool correctly.

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% coverage with clear descriptions for all three parameters. The description adds minimal value beyond the schema, simply restating the 'remember' concept. Baseline 3 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 says 'Keep the memory for later use,' which implies storage but uses the vague verb 'Keep' instead of a more precise one like 'Store' or 'Save'. It distinguishes from the sibling 'qdrant-find' by implying retrieval orientation, but lacks explicit action clarity.

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 includes 'when you are asked to remember something,' providing a condition for use. However, it does not explicitly state when not to use it or directly compare to the sibling tool 'qdrant-find' for retrieval.

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