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 of behavioral disclosure. It only indicates a read operation via 'Get' but fails to specify the return format (plain text? structured object?), error handling (e.g., missing abstract), side effects, or whether the RFC must be loaded first. It provides minimal behavioral context beyond the operation name.

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 extremely brief (6 words) and front-loaded with the key action and resource. While efficient, it is arguably too terse given the lack of annotations and output schema; however, the single sentence does earn its place without redundancy.

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 complex ecosystem of RFC manipulation tools (26+ siblings), nested object parameter, and absence of both annotations and output schema, the description is inadequate. It fails to explain the return value, document prerequisites, or relationships to paired tools like set_abstract.

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% (the 'document' parameter has a description 'RFCDocument'), establishing a baseline of 3. The description adds no additional semantic information about what the RFCDocument object should contain, how to construct it, or what fields are required within the nested object.

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 tool retrieves ('Get') a specific resource ('the abstract') from a specific domain ('RFC document'). While it identifies the target resource precisely, it does not explicitly differentiate from siblings like get_document or get_title, which retrieve different parts of the same document.

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 such as get_document (which likely retrieves the full text) or set_abstract. It lacks explicit when-to-use conditions, prerequisites (e.g., RFC must be loaded), or exclusion criteria.

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