Read Resource (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 safety is covered. The description adds genuinely non-obvious context (this exists only as a fallback path for tool invocation), but says nothing about what happens on failure, what resource is resolved when no parameters exist, or any limits.

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?

One short sentence with no waste, and the defining trait (fallback path) is front-loaded. It is perhaps too terse rather than padded.

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?

Despite an output schema and annotations carrying safety, a zero-parameter resource read needs the description to explain what gets read and how to choose it over `mj_read_resource`/`memory_read_resource`. Neither is present, so an agent cannot confidently invoke it.

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?

There are zero parameters, so the baseline is 4. The empty object schema does raise the question of how the target resource is identified, which the description does not address, but with no parameters there is no semantics to document.

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 identifies the tool as a fallback handler for `read_resource` invoked as an MCP tool rather than a protocol resource read, which is a real distinction. But it never says what a 'resource' is here or what is actually read, and it does not differentiate itself from the near-identical siblings `mj_read_resource` and `memory_read_resource`.

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?

It implies the tool is only for the 'invoked as a tool' path but gives no explicit when-to-use or when-not-to-use instruction, and no mention of the two sibling read_resource tools an agent must choose between. The agent is left to infer routing on its own.

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