batch_store

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

Discloses deduplication and persistence limit of 20 entries. Without annotations, this is helpful. Lacks details on error handling or idempotency, but core behavioral traits are covered.

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, front-loaded with the main action and key benefit. Ideal length for tool descriptions.

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?

Lacks explanation of return value (e.g., success confirmation or error feedback). Does not mention the required 'scope' parameter, leaving ambiguity about its purpose. For a tool with nested input, more detail is needed.

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?

No schema description coverage (0%) and description adds no meaning beyond the schema. Does not explain the purpose of 'scope' or 'source' or the structure of each memory object. Agents would need to infer from names.

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?

Clearly states the tool stores multiple memories with deduplication, distinguishes it from repeated store_memory calls. 'Store multiple memories in a single call' is a specific verb+resource pairing.

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?

Explicitly tells when to use: 'Use when you have several facts to store at once, more efficient than repeated store_memory calls.' Provides clear context and alternative.

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