mcp-rfc-editor

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

With no annotations provided, the description carries the full burden. It mentions 'parse it' which signals the return value is processed/structured, but fails to disclose the optional file-saving behavior (filepath parameter), potential network failures, rate limits, or the specific format of the parsed output.

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 single-sentence description is appropriately sized, front-loaded with the action verb, and contains no redundant or wasteful text. Every word contributes to understanding the tool's core function.

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 simple 2-parameter schema and lack of output schema, the description adequately covers the core operation but leaves gaps regarding the return value structure. Since no output schema exists, the description should ideally clarify what 'parse' produces (e.g., a structured object, text, or dictionary).

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%, establishing a baseline of 3. The description mentions 'by number' which aligns with rfc_id, but adds no additional semantic context for the optional 'filepath' parameter (e.g., explaining when to use file saving vs. just returning parsed data).

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 clearly states the verb (download), resource (RFC), and source (rfc-editor), and mentions parsing. However, it doesn't explicitly distinguish from the sibling 'load_rfc' tool, which likely handles local files versus this external fetch operation.

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 like 'load_rfc' or 'get_document', nor does it mention prerequisites such as network requirements or valid RFC number formats.

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