delimit_context_list

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

Discloses side effects as read-only and the internal call to ai.context_fs. With no annotations, the description does a fair job, though it could mention permissions or error handling. Still, it transparently describes behavior beyond basic purpose.

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 extremely concise with structured sections (purpose, when to use, when not to, sibling contrast, side effects). Every sentence adds unique value, and there is no redundancy or 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?

Given the tool's simplicity (one parameter, output schema present), the description covers all essential aspects: purpose, usage context, alternatives, side effects, and basic behavior. It is fully sufficient for an agent to correctly select and invoke the 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% with a single required parameter 'venture' described as 'Venture namespace key. Required.' The description does not add additional semantic detail beyond what the schema already provides, which is adequate but not enhanced.

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 'List all artifacts in a venture's context filesystem' with a specific verb and resource. It distinguishes from siblings like delimit_context_read (reads content) and delimit_memory_recent (scans memories), leaving no ambiguity about the tool's function.

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?

Explicit when-to-use ('to inventory what artifacts have been written') and when-NOT-to-use sections directly name alternative tools (delimit_context_read, delimit_memory_recent), providing clear decision guidance for the agent.

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