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. It implies a read-only operation via 'Get' but fails to specify the return format (text, structured object, etc.), error handling if the section is absent, or any side effects.

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?

While brief at only six words, the sentence is ambiguous due to the deictic 'this' and lacks front-loaded specificity. The brevity creates under-specification rather than efficient clarity, failing to identify which specific section is being referenced.

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 single parameter with full schema coverage and no output schema, the description meets minimum viability but should explain what constitutes a 'status' or the expected return value format. It leaves agents uncertain about the data type and structure of the returned status information.

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 input schema has 100% description coverage (the 'document' parameter is described as 'RFCDocument'), establishing a baseline of 3. The description adds minimal semantic value beyond the schema, merely implying the document parameter represents 'this memo' without clarifying expected document format or validation rules.

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 the basic action ('Get') and resource ('status of this memo section'), but the use of 'this' is ambiguous in a context-free tool description. It does not clarify that 'Status of This Memo' is a specific standard RFC section, nor does it effectively distinguish from sibling getters like get_abstract or get_title without relying solely on the tool name.

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 (e.g., get_document for the full content), nor does it mention prerequisites such as the document structure or initialization requirements.

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