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

Beyond the annotations, the description discloses all-or-nothing atomicity, write accounting against rate limits, the signed-in session requirement, one transaction id for the whole batch, and pending/confirmed read-back behavior. These are precisely the side effects an agent needs to predict when invoking a batch write 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 dense but well organized: core mechanism first, then item format, atomicity, auth and limits, and finally confirmation behavior. Every sentence contributes actionable information, with the most important transaction-level facts front-loaded.

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?

For a batch write tool with one parameter, the description covers authentication, rate-limit costs, maximum practical batch size, failure atomicity, and return semantics. Since an output schema exists, not restating return fields is appropriate and does not create a completeness gap.

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 schema already documents the `records` parameter, and the description adds operationally significant meaning: items are content_hash plus optional metadata, only hashes and metadata are stored, and callers should treat 10 as the practical batch ceiling even though the schema allows 100. It could be slightly more self-contained on hash rules, but it does point to `store_memory` for the same per-item rules.

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 opens with a specific action and resource: "Anchor many fingerprints in ONE on-chain transaction" and gives the exact record naming format `ai:gh:<github_id>:mem:<content_hash>`. It clearly distinguishes itself from `store_memory` by adding the batch dimension while preserving the same item semantics.

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?

It gives clear context for when batching is appropriate: "a session's worth of artifacts without spending a write per minute on each," and states a hard practical limit of 10 items per fresh minute given free-tier limits. It references `store_memory` as the single-item counterpart but does not explicitly say "use `store_memory` for a single item."

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