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 but fails to specify whether this operation is destructive (overwrites existing content), idempotent, requires specific permissions, or what errors might occur. 'Set' implies mutation but lacks critical safety context.

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 efficiently worded with no redundancy. However, extreme brevity becomes a liability given the lack of annotations and nested object complexity, suggesting the description is under-specified rather than optimally concise.

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?

For a document mutation tool with nested object inputs, no output schema, and no annotations, the 6-word description is insufficient. It fails to explain the relationship between input parameters, side effects on the RFC document, or success/failure behavior.

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 adds no additional context about the 'document' parameter structure (what constitutes an RFCDocument object) or expected format for 'content' (plain text vs. markup). It neither repeats nor enhances the schema definitions.

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 identifies the action ('Set') and target resource ('acknowledgements of an RFC document'), distinguishing it from siblings like set_abstract or set_contributors. However, it lacks specificity about what acknowledgements represent in the RFC context or how they differ from contributors/authors.

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 (e.g., set_contributors), prerequisites (document initialization requirements), or whether this appends to or replaces existing acknowledgements.

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