Tiptap Collaboration MCP Server

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the API usage but doesn't describe error conditions, rate limits, authentication requirements (beyond the appId parameter), whether the conversion is idempotent, or what happens with malformed Markdown. For a tool that performs format conversion with external API calls, this is inadequate.

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 that states exactly what the tool does with zero wasted words. It's appropriately sized for a straightforward conversion tool and front-loads the core functionality.

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 conversion tool with 3 parameters and no output schema, the description is minimally complete. It identifies the transformation but lacks important context about the Tiptap JSON format, error handling, or what the converted output looks like. Without annotations and with no output schema, users must infer behavioral characteristics from the tool name and parameters alone.

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 description mentions 'Markdown content' which maps to the 'content' parameter, but adds no additional semantic context beyond what's already in the schema descriptions. With 100% schema description coverage, the baseline is 3 - the description doesn't compensate but doesn't need to since the schema fully documents all parameters.

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 tool's purpose: converting Markdown content to Tiptap JSON format using a specific API. It includes a specific verb ('Convert') and resource ('Markdown content'), but doesn't explicitly differentiate from sibling tools like 'export_markdown' or 'create_document' which might handle similar content transformations.

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 'export_markdown' (which presumably does the reverse conversion) or 'create_document' (which might accept Tiptap JSON directly). There's no mention of prerequisites, use cases, or comparison with sibling tools.

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