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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Read' and 'org-shared ontology memory,' which implies a safe read operation, but it does not disclose what happens when multiple identifiers are provided, whether it errors on ambiguous inputs, or what the output structure is despite an output schema existing. It also does not clarify auth or sharing semantics beyond 'org-shared.' For a read tool with zero annotation coverage, this is a significant gap.

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 a single, clear sentence with no filler, front-loading the core action and resource. It is concise and to the point, though it could add a little more context without becoming verbose.

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 read tool with an output schema and fully documented parameters, the description is mostly sufficient, but it lacks behavioral guidance on parameter combinations and tool-specific nuances. The output schema covers return values, so that's handled. However, a clearer usage distinction from memory_agent_list or memory_recall would complete the picture. Minimum viable but not fully complete.

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 description coverage is 100%, so the schema already documents all three parameters (name, slug, cursor_agent_id) with their roles. The description adds minimal extra meaning beyond saying 'read memory' and doesn't explain how the parameters interact (e.g., 'omit together with slug/id to fetch the caller' is already in the schema). Baseline 3 is appropriate since the description doesn't contradict or significantly extend the schema.

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?

Description clearly states the action ('Read') and resource ('another agent's (or your own) org-shared ontology memory'), which is specific enough. It is distinct from siblings like memory_agent_list (which likely lists memories) and memory_agent_ensure/set (which write), though it doesn't explicitly name them.

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 usage for reading ontology memory, and the parameter docs hint that omitting identifiers fetches the caller, giving a sense of when to use defaults. However, it does not explicitly say when to prefer this over siblings like memory_recall or memory_agent_list, nor does it provide exclusions or routing guidance. This is implied by the resource name but not stated.

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