read_result

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

With no annotations, the description must disclose behavioral traits. It states 'Read' implying idempotence but does not mention error behavior for missing IDs, rate limits, data freshness, or whether it returns the full object. This is insufficient for a mutation-free tool.

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 sentence that is front-loaded with the core action. It contains no redundant words, achieving high conciseness. However, it sacrifices detail for brevity.

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 has one parameter and no annotations, the description omits important context: how to obtain a result_id, error handling, and what the read operation entails (e.g., is it a full object or summary?). Having an output schema reduces the need to describe returns, but usage and parameter context are lacking.

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 0%, and the description only says 'by result_id' without explaining what result_id is (e.g., format, example, where to obtain it). The parameter remains semantically opaque, forcing reliance on the schema which only gives type 'string'.

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 'Read a stored MCP result by result_id' clearly states the verb (Read), the resource (stored MCP result), and the method (by ID). It effectively distinguishes from siblings like list_results (which lists all) and export_result (which exports).

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention prerequisites, such as needing a result_id from a prior MCP call, nor does it contrast with siblings like list_results or export_result.

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