mcp-rfc-editor

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. While 'Delete' implies a destructive operation, the description fails to specify critical safety details: whether subsections are recursively deleted, if the operation is reversible, or what happens to remaining section numbering. This is insufficient for a destructive mutation tool.

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 is front-loaded and wastes no words. However, extreme brevity for a destructive operation with nested object parameters is arguably a structural weakness rather than a virtue, as it leaves critical safety and behavioral context unstated.

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 destructive nature of the operation, the presence of a nested object parameter (document), and the absence of annotations or output schema, the description is incomplete. It should disclose structural impact (subsection handling) and safety implications to be considered minimally complete for an agent selecting destructive tools.

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?

With 100% schema description coverage, the structured data already documents that 'document' is an RFCDocument and 'number' is the section identifier. The description adds no additional parameter context (e.g., format expectations for the section number, whether the document object must be loaded first), warranting the baseline score.

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 uses a specific verb ('Delete') and clear resource ('section from an RFC document'), making the core purpose immediately understandable. However, it lacks explicit differentiation from sibling tools like 'update_section' or 'set_section_by_title' that might also modify document structure.

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., when to delete vs. update a section), nor does it mention prerequisites such as whether the section must be empty or if confirmation is required before deletion.

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