processon_md_to_mindmap

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

With no annotations, the description carries the full behavioral disclosure burden. It does disclose that only headings and bullet lists are parsed, and that an empty title is auto-generated. However, it does not state that this likely creates a persistent mindmap resource, nor does it mention authentication, rate limits, or side effects. This is a notable gap for a tool that presumably performs a write operation.

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 one-sentence purpose is front-loaded, followed by a brief elaboration and a well-organized 'Args' section. The structure list is somewhat long but necessary given the empty schema descriptions. Each sentence earns its place; no filler or repetition.

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 an output schema, the description covers the essential inputs and behaviors: Markdown format, title default, and layout options. The main missing piece is side-effect and authentication context, which would matter without annotations. Overall, it is adequate but not exhaustive.

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 0%, so the description fully compensates. Each parameter is explained: markdown's expected content, title's auto-generation behavior, and structure's allowed values with both English and Chinese labels. This goes well beyond the schema, which only provides types and defaults.

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 opens with a specific verb and resource: 'Convert Markdown text into an editable ProcessOn mindmap.' It then specifies the input format (headings and bullet lists) and the output (editable online mindmap), making its role distinct from siblings like processon_render_mermaid, which targets Mermaid rendering. The purpose is unambiguous.

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 gives clear context: 'Great for turning meeting notes, an outline, or a document summary into a visual mindmap.' This tells an agent when this tool is appropriate. It does not explicitly name alternatives or exclusions, but the use case is concrete enough that an agent can choose it over the other processon tools.

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