Ingest Markdown Conversation

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

Annotations indicate idempotentHint: true, but the description does not mention idempotency or behavior on re-ingestion. It adds the file-handling caveat but lacks detail on side effects or performance characteristics. Adequate but could be improved.

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?

Two sentences that are front-loaded with purpose and a critical usage note. No extraneous information, 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?

While the tool has an output schema (so return format is covered), the description omits explanation of optional parameters like nest, branch, agent_id, and response modes. For a tool with 7 parameters, this leaves gaps for new users.

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 coverage is low (only 29% of parameters have descriptions). The description only implicitly references content and source_label, ignoring nest, branch, agent_id, terse, and response_format. This provides little added value for parameter understanding.

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 action: 'Ingest a Markdown conversation export into memory entries and knowledge graph triples.' It specifies the resource (Markdown conversation) and outcome (memory and KG entries), distinguishing it from sibling tools like localnest_ingest_json for JSON input.

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?

Provides explicit guidance: 'Pass the full text content directly — file reading is handled by the CLI, not MCP tools.' This tells the agent to avoid file reading and to pass raw markdown text. Slightly lower score because it does not explicitly state when not to use or list alternatives, though the context is clear.

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