mcp-rfc-editor

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

No annotations are provided, so the description carries full disclosure burden, but it fails to indicate that this is a destructive write operation (overwrites existing abstracts), whether it requires authentication, or if the operation is idempotent. The single sentence 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 a single, front-loaded sentence of eight words with zero redundancy. Every word earns its place by conveying the essential operation, target field, and domain context without filler.

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 two-parameter mutation tool with 100% schema coverage and no output schema, the description is minimally adequate. However, given the lack of annotations and the nested object parameter (document), it omits helpful context about what constitutes a valid RFCDocument reference and whether the operation performs validation.

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 ('RFCDocument' and 'Abstract text'), the baseline is 3. The description adds no additional semantic value regarding parameter formats, validation rules, or the nature of the document reference (ID vs object), merely restating the obvious mapping between description and schema fields.

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 provides a specific verb ('Set'), clear resource ('abstract'), and context ('RFC document'). It effectively distinguishes this tool from sibling 'get_abstract' through the action verb, clarifying this is a write operation versus a read operation.

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?

While the setter naming convention implies use for modifying existing RFCs (complementing 'get_abstract'), the description provides no explicit guidance on prerequisites (e.g., document must exist), when to use 'create_rfc' versus this tool, or validation constraints on the abstract text.

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