delimit_context_write

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

No annotations provided, but description discloses side effect (file creation under ~/.delimit/context/<venture>/) and notes that artifact_type only affects render hints. Could mention overwrite behavior or size limits for a 5.

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?

Every sentence serves a purpose: action, when-to, when-not-to, sibling contrast, side effects. No extraneous words; front-loaded with core purpose.

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?

Covers purpose, usage, side effects, and sibling differentiation. Output schema exists but is not shown; description does not need to return values. Missing concurrency or error details, but sufficient for a write 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?

Schema coverage is 100%, so baseline 3. Description adds value by explaining that artifact_type affects render hints but not storage format, and implies name is the file key. Adequately complements 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 uses specific verb 'Write' and resource 'artifact to a venture's context filesystem', clearly distinguishing from siblings like delimit_context_read, delimit_context_list, and delimit_context_snapshot.

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?

Explicitly states when to use (persist plans/decisions/code for future sessions) and when not to (ephemeral context, snapshot all), with named alternatives: delimit_memory_store and delimit_context_snapshot.

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