import_content

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

No annotations are provided, so the description carries the burden. It discloses the side effect of storing content with source tracking and notes that source_fetched_at is auto-set, which is useful. However, it doesn't describe what happens on overwrite of an existing ref, whether this mutates or supplements existing snapshots, or the return shape.

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 tight — three short sentences with no waste. The usage guidance is front-loaded in the first sentence, and the technical cue (source_fetched_at auto-set) earns its place as it informs agent expectations. Slightly verbose 'then ContextForge owns it as a snapshot' but acceptable.

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?

The tool is a write/import with 4 parameters (100% schema coverage) and an output schema present. The description covers the core workflow (post-fetch import), source tracking, and a key side-effect (source_fetched_at auto-set). Remaining gaps like overwrite behavior are minor for a well-documented schema with output schema.

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 baseline is 3. The description adds meaning to source_url ('canonical') and source_name (gives example values 'confluence', 'notion', 'github-wiki'), and explains the source_fetched_at auto-fill behavior tying into the schema semantics.

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 uses a specific verb+resource ('Store content fetched from an external source as a subtopic') and clearly connects it to the sibling tools for Confluence fetching. It distinguishes itself from append_context/upsert_context by framing itself as the snapshot-owner for external fetches with source tracking.

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 explicitly states when to use it: 'after another MCP tool returns page content', naming an example (Atlassian MCP for Confluence). It implies ContextForge then owns the snapshot, distinguishing from alternative write tools, though it doesn't explicitly name alternatives or exclusions.

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