nero_memory_read

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

No annotations provided; description only states it reads entries, implying read-only behavior. It does not disclose edge cases (e.g., missing key, empty results) or any side effects, but there is no contradiction.

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 concise sentences front-load the purpose and cover all modes. No filler or redundancy.

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?

Adequately describes the three read modes for a simple tool with optional params and no output schema. Missing mention of behavior on missing keys, but sufficient for many agent scenarios.

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% with descriptions for both parameters. The tool description largely repeats the schema info (e.g., 'Read all keys starting with this prefix' matches schema). No additional semantic value added beyond what the schema provides.

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 clearly states 'Read entries from the shared memory bus' with three explicit modes: specific key, prefix, or all entries. This distinguishes it from sibling tools like nero_memory_write (write) and nero_memory_dump (dump).

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 implies when to use each mode (key, prefix, or no params) but does not explicitly guide the agent on when to prefer this over nero_memory_dump or other siblings. No mention of when not to use this tool.

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