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 'Set' implies mutation, the description fails to specify whether this overwrites existing titles, modifies the document in-place versus returning a new object, or has 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?

The single-sentence description is appropriately brief and front-loaded with the action verb. However, given the complete absence of annotations and output schema, this extreme brevity leaves critical gaps rather than achieving efficient communication.

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 two-parameter mutation tool with nested objects and no output schema or annotations, the description provides only minimal viable context. It omits whether the modified document is returned, error conditions, or persistence behavior.

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%, adequately documenting the RFCDocument object and title string. The description reflects these parameters but adds no additional semantic context such as title format constraints or whether the document parameter expects an ID or full 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 'Set the title of an RFC document' provides a specific verb (Set) and resource (title). It implicitly distinguishes from sibling get_title through verb choice, but does not explicitly differentiate from other setters like set_abstract or clarify scope limitations.

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 contains no guidance on when to use this tool versus alternatives (e.g., get_title for reading), prerequisites (e.g., document must exist), or when not to use it.

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