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 only implies read-only safety through the verb 'Get'. It fails to describe the return format, error behavior when the section is missing, or whether the operation is idempotent.

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, efficient sentence with no wasted words. However, given the complexity of RFC document structures and the lack of an output schema, it may be overly terse rather than appropriately 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?

Despite having a nested object input and no output schema, the description does not explain the expected structure of the RFC document, the format of the returned address data, or error handling. It relies entirely on the tool name and schema, leaving significant gaps for an AI agent.

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 (the single parameter is described as 'RFCDocument'), establishing a baseline score. The description adds no additional parameter semantics, usage examples, or details about what constitutes a valid RFCDocument 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 uses a specific verb ('Get') and clearly identifies the target resource ('authors address section' of an RFC document). It implicitly distinguishes from siblings like 'get_authors' by specifying 'address section', though it does not explicitly contrast with them or explain the difference between author names and addresses.

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 like 'get_authors', nor does it mention prerequisites such as loading the document first. There are no exclusions or conditions mentioned for proper invocation.

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