insp_resources_read

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 states 'Read a specific resource,' implying a read-only operation, but doesn't cover critical aspects like authentication needs, rate limits, error handling, or what the output looks like (e.g., raw data, structured format). For a tool with 6 parameters and no output schema, this is a significant gap in transparency.

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 that directly states the tool's purpose. It's front-loaded with the core action ('Read a specific resource') and avoids unnecessary details. Every word earns its place, making it highly concise and well-structured for quick understanding.

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?

Given the tool's complexity (6 parameters, nested objects, no output schema) and lack of annotations, the description is incomplete. It doesn't explain the resource type, how parameters like 'transport' affect behavior, or what the read operation returns. For a tool that likely involves server interaction and resource retrieval, more context is needed to guide effective use.

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%, meaning all parameters are documented in the input schema. The description adds no additional meaning beyond the schema, such as explaining how parameters interact (e.g., 'command' vs. 'url' for transport) or providing examples. With high schema coverage, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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 states the tool 'Read a specific resource from an MCP server,' which clearly indicates a read operation on a resource. However, it doesn't specify what type of resource (e.g., file, data object) or differentiate from sibling tools like 'insp_resources_list' (which likely lists resources) or 'insp_resources_templates' (which might handle templates). The purpose is clear but lacks sibling differentiation.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., server setup), exclusions (e.g., not for writing), or compare to siblings like 'insp_resources_list' for listing resources. Without such context, an agent might struggle to select the correct tool in a given scenario.

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