delimit_context_write

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'write', implying a destructive operation, but does not clarify whether it overwrites existing artifacts, if there are access restrictions, or any side effects. This is insufficient for safe invocation.

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 a single sentence with no wasted words, but it is excessively terse. It achieves conciseness at the expense of necessary details, making it less helpful.

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?

Given the tool's complexity (4 parameters, including a required 'name' and 'content'), the description is too brief. It does not explain return values (though output schema exists), nor the meaning of 'artifact_type'. The description fails to provide a complete understanding needed for correct usage.

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?

The input schema has 4 parameters with 0% description coverage in the schema. The description adds no meaning beyond the parameter names. For example, 'venture' and 'artifact_type' are not explained, so the agent must infer their purpose from context.

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 'Write an artifact to the context filesystem' clearly states the action (write) and the resource (artifact to context filesystem). It distinguishes the tool from siblings like delimit_context_read and delimit_context_list. However, it lacks specificity about what constitutes an 'artifact' in this context, which could be improved.

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 provides no guidance on when to use this tool versus alternatives such as delimit_context_branch or delimit_context_init. It does not mention prerequisites, excluded cases, or related tools.

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