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

The description adds extensive behavioral details beyond annotations: it specifies that rows append (not overwrite), data persists across calls/deploys/restarts, identity is wallet-based without keys/accounts, activity extends collection lifetime, and includes explicit limits (16KB/row, 1000 rows/call, etc.). No contradiction with annotations.

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?

Every sentence adds value: purpose, input formats, behavior, limits, pricing. It is dense but clear, front-loaded with the key action. No wasted words.

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?

Given the presence of an output schema (not shown but indicated), the description does not need to explain return values. It covers input, behavior, limits, pricing, and identity model comprehensively for a write tool.

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 only parameter 'collection' is fully described in the schema (100% coverage) with URL path format. The description repeats this but adds no new semantics; it mentions the collection is 'owned by your paying wallet' but that is behavioral context, not parameter-specific. 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 starts with 'AGENT DATASTORE — append rows to your wallet's persistent storage,' clearly stating the action (append) and resource (rows to a collection). It distinguishes from sibling tools like get_store_collection (read) and delete_store_collection (delete) by emphasizing the write/persist nature.

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 context: 'Give your agent a memory' and explains persistence and activity-based expiration. It implies when to use (storing data) but does not explicitly state when not to use or list alternatives. However, the context is sufficient for an agent to decide.

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