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 deliver. It does not state whether this overwrites existing status text, whether there are validation constraints on the status value, or if the operation is idempotent. No side effects or return behavior is documented.

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 brief (6 words), but the use of 'this' is potentially confusing without conversational context, and the phrasing wastes an opportunity to clarify the RFC domain. It is appropriately short but not optimally structured for clarity.

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 mutation tool with nested object parameters and no output schema, the description is inadequate. It fails to explain what constitutes a valid RFCDocument object, what the 'Status of This Memo' section represents, or what success/failure looks like. Given the complexity implied by the nested document structure, more context is needed.

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?

The schema has 100% description coverage (document: RFCDocument, status: Status text), establishing a baseline of 3. The description adds no additional semantic value regarding the structure of the RFCDocument object, valid status values, or formatting requirements beyond what the schema 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 states the basic action (Set the status) but uses ambiguous phrasing ('this memo section') that assumes domain knowledge of RFC document structure. It does not clearly indicate this operates on the 'Status of This Memo' section of an RFC document passed via the document parameter, nor does it explicitly distinguish from sibling tools like set_section_by_title.

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 is provided on when to use this tool versus alternatives (e.g., when to set vs. get status), nor are prerequisites mentioned (e.g., document must exist). The description lacks explicit exclusions or workflow context.

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