mcp-rfc-editor

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Get' implies a read-only operation, the description fails to specify the return format (string vs. object), error behavior when title is missing, or whether the operation is idempotent. This leaves significant behavioral gaps for a tool with no annotation coverage.

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 consists of a single, efficient sentence with no wasted words. It is appropriately front-loaded with the action and target. However, given the lack of annotations and output schema, the extreme brevity contributes to informational gaps, though the sentence itself is well-structured.

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 single-parameter getter tool, the description meets minimum viability by identifying the core operation. However, given the nested object parameter type (RFCDocument), absence of annotations, and lack of output schema, the description should elaborate on acceptable document input formats and return types to be fully complete.

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 'document' parameter is typed as 'RFCDocument'), the baseline is 3. The description mentions 'RFC document' which aligns with the parameter name and schema type, but adds no additional semantic context about the expected object structure, whether it requires a document handle, or how to obtain the document object.

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 a specific verb ('Get') and resource ('title of an RFC document'), clearly distinguishing it from the sibling 'set_title' through the action verb and from other field accessors like 'get_abstract' by specifying the target field. However, it lacks explicit differentiation from 'get_document' which retrieves the full document.

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 such as extracting the title from the full document returned by 'get_document' or 'to_dict'. It omits prerequisites (e.g., whether the document must be loaded first) and gives no 'when-not' exclusions.

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