import_markdown_context

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

With no annotations, the description carries the full burden, and it does disclose real quirks: headings become elements, and checkbox syntax/state is stripped for non-TODO maps. However, it does not say whether the import appends to or replaces existing map content, whether the operation is idempotent or reversible, or what happens on invalid mapId — notable gaps for a mutation tool.

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 core action and format expectations are front-loaded in the first sentence, followed by the behavioral exceptions. It is dense but each sentence adds a distinct rule; only minor phrasing could be tightened.

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 3-parameter mutation tool with no annotations and no output schema, the description covers format, tree semantics, and prerequisites well, but omits append-vs-replace semantics and error/return behavior. It is adequate but leaves the agent guessing on state-changing side effects.

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%, so mapId, markdown, and parentElementId are already documented in the schema. The prose adds only the implicit idea that content lands inside parentElementId (or at top level if omitted), matching what the schema already says, so the baseline 3 is appropriate.

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 names a specific verb (build/stream Markdown into a map) and resource (an existing map), and immediately clarifies the flattening rule that headings count as elements. It is clearly distinguishable from siblings like create_map and edit_element because it operates on a whole Markdown tree rather than single elements.

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?

It explicitly states the target must be an existing map and names the alternative ('if you need a new one, call create_map first'), which routes the agent correctly. It also gives the condition under which checkbox notation is dropped, though it does not discuss when to prefer this over editing elements individually.

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