Read Resource (memory_read_resource Autonomous Fallback)

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the bar is lower. The description contributes one genuine piece of context beyond annotations – that this is a fallback invocation path rather than a normal tool – but says nothing about the return payload, failure behavior, or what happens if no resource context exists.

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?

A single front-loaded sentence with no padding; the framing as a fallback is stated immediately. It is efficient, though the terseness contributes to the opacity noted elsewhere.

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?

An output schema and annotations cover the return shape and safety profile, so those are not the issue. What is missing is any explanation of the implicit resource target and the relationship to the two sibling resource-read tools, which is exactly the information needed to decide whether calling this does anything meaningful.

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 tool takes zero parameters, which would normally put this at baseline 4. However, a resource-read operation with no way to specify a resource is inherently ambiguous, and the description does not explain that the target is supplied implicitly by protocol context – leaving the agent unable to reason about what it would even read.

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 says it is a 'fallback handler' for reading a resource, which gives a rough verb+resource, but it never states what a resource is in this system or what gets read. It also does not distinguish itself from the near-identical siblings `read_resource` and `mj_read_resource`, so an agent cannot tell the three apart from the description alone.

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 only usage information is the trigger condition 'when invoked as an MCP tool instead of a protocol resource read', which describes when the harness routes here rather than giving the agent guidance. There is no statement of when an agent should call this versus `read_resource`, `mj_read_resource`, or `get_entry_by_id`.

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