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

Annotations only flag readOnly=false, etc., but the description adds crucial context: cost per call, payment-as-authentication, namespace ownership, TTL expiration, delete operation, max value size, and hosted vs self-hosted modes. It clearly discloses mutation and idempotency implications without contradicting 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?

Dense but every sentence earns its place: cost/auth upfront, usage semantics, alternatives, examples, and hosting options. No filler, logically ordered, and front-loaded with the most important operational facts.

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 complexity (payment, namespaces, TTL, delete, size limits, output schema), the description covers all essential operational details including return fields. The existence of an output schema reduces the need to detail return structure further, so nothing critical is missing.

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 coverage is 100%, so baseline is 3. The description goes further by explaining how parameters combine (e.g., 'optional TTL', 'delete:true to remove', 'owner:0x…' for grants) and gives the exact body format, adding contextual meaning beyond the schema's per-property descriptions.

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 specific verb (write), resource (persistent key-value memory), and scoping (paying wallet). It clearly distinguishes from siblings memory-remember/memory-recall by contrasting exact-key storage vs retrieval by meaning, so an agent can differentiate without opening schemas.

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 says when to use this tool vs alternatives: 'when you want retrieval by MEANING rather than key, use memory-remember + memory-recall instead' and also explains write/delete/owner behaviors. Conditions for writing into other namespaces are given, leaving nothing to inference.

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