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 fails to state whether this is read-only (implied by 'List' but not explicit), what the return format is (list of titles? full objects? IDs?), or whether there are any performance considerations for large documents.

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 with the action verb and contains no redundant words. However, given the lack of annotations and output schema, the description 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?

For a single-parameter tool without output schema, the description covers the basic operation but leaves gaps regarding return value structure and content scope. It meets minimum viability but does not compensate for missing output documentation.

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 description coverage is 100% (the document parameter is described as 'RFCDocument'), so the baseline is 3. The description adds minimal semantic value beyond the schema, merely confirming the parameter represents an RFC document without clarifying the expected structure or how to obtain/construct this 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 clearly states the verb (List) and resource (sections in an RFC document). However, it does not explicitly distinguish from siblings like get_section_by_title (which retrieves a specific section) or get_toc (which may also list section titles), though the 'all' implies broad scope.

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?

No guidance provided on when to use this tool versus alternatives. The description does not clarify when to prefer list_sections over get_section_by_title for specific lookups, or whether this returns full section content or just metadata/headings.

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