Export network docs to the vault

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

Discloses that the note is 'fully rewritten on each call', which is a key behavioral trait. Returns note path, node/connection counts, and truncation status. Annotations (readOnlyHint=false, destructiveHint=false) are consistent with description. No contradiction.

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?

Description is a single paragraph but efficiently covers purpose, usage guidance, and return values. Front-loaded with key action. Every sentence adds value; no fluff.

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 tool with 3 parameters, no output schema, and moderate complexity, the description fully addresses what the tool does, when to use it, what it returns, and any prerequisites. No gaps.

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 100%, so schema already documents parameters well. Description adds context that note defaults to 'Networks/<path>.md', which enriches understanding beyond the schema. Slight extra value beyond 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?

Description explicitly states the action ('READ' and 'WRITE'), the resource (TD network), and the output (Obsidian note with Mermaid flowchart and wikilinks). It distinguishes from sibling tool document_network by specifying that this tool persists to vault while the other returns results. Very clear and specific.

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: 'Use this to persist a browsable map in the vault; use document_network to get the same documentation back as a tool result without touching the vault.' Also mentions prerequisite: 'Requires a configured TDMCP_VAULT_PATH.' No ambiguity.

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