mcp-rfc-editor

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

With no annotations provided, the description carries full disclosure burden. It mentions parsing sections but fails to specify whether this loads the RFC into a workspace state for subsequent sibling operations, what the return format is, or failure modes (e.g., file not found). The stateful side effects are undocumented.

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?

Extremely concise at nine words in a single sentence. No filler or redundancy; every word earns its place describing the core action.

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 extensive ecosystem of sibling tools for section manipulation, the description inadequately establishes `load_rfc` as the entry point that enables subsequent operations. Without an output schema, the description should clarify the relationship to the broader RFC manipulation workflow, which it omits.

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 coverage is 100% and the description adds minimal semantic value beyond the schema. It implies a local file path via 'TXT file' (distinguishing from URLs), but provides no additional constraints (absolute vs. relative) or format details beyond what the schema 'Path to RFC TXT file' already provides.

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 (Load) and resource (RFC TXT file) and specifies the action taken (parse its sections). However, it does not explicitly distinguish this from sibling `download_rfc` (local file vs. network fetch) or clarify that this is for existing files vs. `create_rfc`.

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 provided on when to use this tool versus `download_rfc` for fetching RFCs remotely, or how it relates to the workflow involving `get_section_by_title` and other manipulation tools. The agent cannot determine prerequisites or alternatives from the text.

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