delimit_ledger_context

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

With no annotations, the description carries the full burden. It declares 'Side effects: read-only' and 'Calls ai.ledger_manager.get_context', which is useful. However, it doesn't detail error conditions or the exact return structure (though output schema exists). A 4 is appropriate for adding good behavioral context beyond the schema.

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, well-structured, and front-loaded with the core purpose. Every sentence adds value, including separate sections for usage guidelines, sibling contrast, and side effects. No unnecessary words.

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 optional parameter, clear purpose), the description covers purpose, usage, exclusions, side effects, and implementation. It is complete enough for an agent to know when and how to use it. Minor omission: no mention of error handling or empty state, but overall sufficient.

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 the input schema already fully describes the single optional parameter `venture` with default and auto-detection. The description does not add additional meaning or constraints beyond what the schema provides, so a baseline 3 is correct.

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 the tool returns a 'Quick summary of what's open in the ledger (top 5 by priority)', providing a specific verb, resource, and scope. It also distinguishes from siblings by contrasting with delimit_ledger_list (full list) and delimit_ledger_query (specific item).

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 ('at session start as part of the orchestrator session ritual') and when NOT to use ('for the full list... or to fetch a specific item'), including alternative sibling tools. This provides excellent guidance.

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