evidence_batch_insert

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only restates the insert operation and does not surface important behaviors such as the atomic/dry_run options, partial-failure semantics, or the default non-atomic commit behavior. The schema defines these flags, but the description itself adds no transparency beyond the obvious write operation.

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, front-loaded sentence with no filler. It immediately names the verb and resource while conveying the core batching distinction. Every word 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 schema fully documents all parameters and an output schema exists, so the tool definition is structurally complete. However, the description itself is bare: it offers no usage context, no behavioral guardrails, and no hint about batch limits or error behavior. The overall definition is minimally adequate but leaves the agent to infer when and how this tool should be used.

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 does not add parameter-specific meaning beyond what the schema already provides: 'multiple records' is consistent with the records field but not more informative than its schema description. No compensation is needed given full coverage.

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 a concrete action (insert), the object (records), the target (an evidence), and the batch nature (multiple in a single request). This clearly distinguishes it from single-record creation (evidence_create) and batch update (evidence_batch_update).

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 gives no guidance on when to use this tool versus alternatives like evidence_create or evidence_batch_update. It does not mention any tradeoffs, limits, or exclusion conditions; the only hint is the word 'multiple,' which implicitly suggests batch use but is never made explicit.

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