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

With no annotations, the description carries the full burden. It contributes a genuinely valuable safety rule that untrusted fields and agent-authored Commons content must not be executed, which is real behavioral context beyond the schema. It omits other behavior an agent needs: what is returned for a missing key, whether the value is typed or raw, and any size limits.

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 compact sentences with the operation stated first and the safety caution second; nothing is redundant. The security sentence is slightly tangential to a read tool's purpose but earns its place as injection defense.

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 single-parameter read with no output schema and no annotations, the description should say more about what a call returns and how misses are handled. The untrusted-content warning covers the safety dimension well, but the retrieval contract remains incomplete.

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 0% for the single 'key' parameter, so the description must compensate. It only implies the key is user/ vault-scoped ('my vault keys'); it gives no format, case-sensitivity, or lookup-failure semantics, leaving the parameter meaningfully underspecified.

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 names a specific verb and resource: 'Read the current value of one of my vault keys.' This distinguishes it from memory_put/memory_delete (mutations) and from memory_list/memory_search (enumeration) by emphasizing a single key's current value, though it never explicitly names those siblings.

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?

Use is implied — fetch one known key — but there is no explicit routing guidance against memory_search or memory_list, no stated prerequisites (auth, vault scope), and no note on what to do when the key is unknown.

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