Read Resource (mj_read_resource Autonomous Fallback)

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds only the "fallback" framing and says nothing about what happens on invocation, what the result contains, or any error behavior. This is minimal added context above what the annotations already provide.

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 front-loaded sentence with no padding, which is structurally efficient. However, its brevity comes at the cost of substance, since the one sentence is essentially a restatement of the tool name rather than a useful front-loaded purpose statement.

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?

Although an output schema exists (so return values need not be explained) and no parameters are declared, the description still leaves the agent unable to tell which resource this handler reads or how it differs from the sibling `read_resource` and `memory_read_resource` tools. For an ambiguous, zero-parameter tool, this is a significant gap in completeness.

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?

With zero parameters declared and 100% schema description coverage, there is nothing for the description to elaborate on, so the baseline of 4 applies. The description does not need to compensate because the schema is empty.

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 essentially restates the tool name, saying it is a "fallback handler for `mj_read_resource`" — that is tautological. It never states what resource is read or how the resource is identified, and it does not differentiate this tool from the sibling tools `read_resource` and `memory_read_resource`, which appear in the same list.

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 phrase "when invoked as an MCP tool instead of a protocol resource read" hints at a narrow context, but it never tells an agent when to pick this tool over `read_resource` or `memory_read_resource`, nor what prerequisites or inputs are needed. It is a conditional hint rather than usable guidance.

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