agent.memory.get

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

The description discloses return values (value, etag, sizeBytes, timestamps) and error conditions (404 if missing/expired). With no annotations provided, this adds valuable behavioral context beyond the input schema.

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 extremely concise with two sentences. It front-loads the primary purpose and covers key details without extraneous information.

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 simple read tool with one parameter and no output schema, the description is complete. It explains the action, return fields, and an important error condition (404). No further context is necessary.

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 description mentions 'by key,' indicating the role of the key parameter. However, it does not add additional meaning beyond what the schema provides (e.g., format, length, or constraints). With schema description coverage at 0%, the description is adequate but not richer.

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 a memory entry by key,' specifying the resource (memory entry) and action (read). It distinguishes itself from sibling tools like put, delete, and list, which have different purposes.

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 does not provide explicit guidance on when to use this tool versus alternatives (e.g., agent.memory.list, agent.memory.put). There is no mention of when not to use it or specific prerequisites.

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