delimit_ventures

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

The description states 'Side effects: read-only' and 'Calls ai.ledger_manager.list_ventures', disclosing the underlying implementation and the read-only nature. Since no annotations are provided, this fully covers behavioral expectations.

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 concise and well-structured with clear sections: summary, usage guidelines, sibling contrast, side effects, args, returns. Every sentence adds value without redundancy.

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 zero-parameter tool with an output schema, the description covers all necessary context: purpose, usage boundaries, side effects, and return shape. It is fully self-contained and requires no additional inference.

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 description explicitly lists 'Args: None' for the zero-parameter tool, which aligns with the empty input schema. It also describes the return value structure. Following the guideline for 0 params, a baseline of 4 is appropriate.

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 registered ventures (auto-registered project directories)', specifying the action (list) and resource (ventures). It distinguishes from sibling tools by later explaining that delimit_context_list inventories artifacts inside a venture, while this lists ventures themselves.

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 provides 'When to use' and 'When NOT to use' sections, giving concrete scenarios and naming alternative tools (delimit_context_list, delimit_memory_recent). This guides the agent on appropriate invocation.

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