velixar_import

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

With no annotations, the description bears full responsibility. It discloses the 50-item limit and conflict handling, which are important behavioral traits. However, it does not mention whether the operation is idempotent, what happens on partial failures, or any authentication/permission requirements. More behavioral context would be beneficial.

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 covering purpose, limit, and conflict handling. No unnecessary words or repetition. Information is front-loaded with the key action 'Bulk import memories from structured data'.

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 has 6 parameters and no output schema. The description covers the main purpose, a key constraint (max 50), and conflict strategies. However, it lacks details on return value (e.g., count of imported items) and error handling. Given the complexity, a bit more information would improve completeness.

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 baseline is 3. The description adds value beyond the schema by stating the max 50 items per call and summarizing the conflict strategies. While the schema already documents each parameter, the description provides critical constraints and context that are not in the schema.

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 does bulk import of memories from JSON or Markdown. It uses the specific verb 'import' and resource 'memories', and the title 'velixar_import' reinforces this. It distinguishes itself from siblings like 'velixar_store' (likely single item) by focusing on bulk operation and structured formats.

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 provides clear guidance on when to use this tool: for bulk imports (max 50 items). It also mentions conflict detection strategies (skip, overwrite, merge), which helps the agent choose the appropriate strategy. However, it does not explicitly state when not to use it or mention alternatives like 'velixar_store' for single items.

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