mcp-rfc-editor

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

No annotations provided, so description carries full disclosure burden. While 'Save... to a TXT file' implies file system mutation, it omits crucial behavioral details: overwrite behavior, encoding, error handling on disk full, or whether the operation is atomic. Inadequate for a destructive file-write operation.

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 9 words, front-loaded with the action verb. No wasted text. However, the brevity contributes to under-specification given the tool's behavioral complexity (file I/O with side effects) and rich sibling context.

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 this is a file-writing tool with no annotations and numerous siblings (create_rfc, load_rfc, download_rfc), the description is insufficient. It lacks: relationship to prerequisite tools, file system safety warnings, or return value description (though no output schema exists).

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%, establishing baseline 3. The description adds minimal value beyond the schema—only specifying 'TXT file' format hint for the filepath parameter. Does not elaborate on the RFCDocument structure requirements or constraints beyond the schema's 'RFCDocument to save'.

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 (Save) and resource (RFC document) with specific format (TXT file). However, it does not explicitly differentiate from siblings like create_rfc (in-memory creation) or download_rfc (network fetch), which could cause confusion given the extensive sibling toolset.

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 alternatives like download_rfc, nor prerequisites (e.g., that an RFC document object must exist from create_rfc or get_document before saving). Missing critical context for agent selection.

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