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. While 'Get' implies a read-only operation, the description fails to specify safety guarantees, idempotency, authentication requirements, or what is returned when acknowledgements are absent. It lacks critical behavioral context for a data retrieval 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 description is a single, efficient sentence with no redundant words. It is appropriately front-loaded with the verb and delivers the core purpose immediately without wasting tokens.

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 simple single-parameter input and lack of output schema, the description is minimally adequate but incomplete. It fails to describe the return value format (string, object, list) or error states, which would be especially valuable since no output schema exists to document the response structure.

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?

Schema coverage is 100% (the 'document' parameter is typed as RFCDocument), establishing a baseline of 3. The description adds no additional semantic clarity about the parameter (e.g., whether it expects a document ID, file path, or object reference), relying entirely on the schema definition.

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 clearly identifies the action ('Get') and the specific resource ('acknowledgements of an RFC document'). However, it does not explicitly differentiate from sibling tools like set_acknowledgements or clarify scope constraints (e.g., whether it returns raw text or structured data).

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_document (which might return the full RFC) or set_acknowledgements. It omits prerequisites, error conditions (e.g., document lacks acknowledgements), and sequencing context.

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