create_mindmap_canvas

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

The description adds no behavioral details beyond the basic 'generate' action. It does not disclose whether the tool creates a new canvas element, how it affects existing content, or any side effects. Annotations already indicate it is a non-read, non-idempotent operation, so the description contributes little additional transparency.

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, front-loaded sentence with no redundant words or filler. It communicates the core purpose efficiently and every word earns its place.

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 tool has five parameters, annotations, and an output schema, the description is minimally adequate. It states the purpose but lacks operational context such as how parameters like sub topics and markdownList interact, or what happens on creation. The schema and annotations cover structured aspects, but the description could be more complete for a create-type tool.

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?

All five parameters have schema descriptions (100% coverage), so the description does not need to explain them individually. The description mentions 'markdown nested list', which loosely relates to markdownList, but it adds no meaningful parameter semantics beyond the schema.

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 generates a structured markdown nested list mindmap for AFFiNE edgeless canvas, combining a specific verb ('generate') with a distinct resource ('mindmap for AFFiNE edgeless canvas'). This distinguishes it from sibling tools like create_doc or add_surface_element.

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 implies the use case: you would use this tool when you need to create a mindmap on the edgeless canvas. However, it provides no explicit when-to-use or when-not-to-use guidance, no alternatives, and no prerequisites or exclusions.

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