delimit_ledger_context

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

Describes output as top 5 by priority. No side effects or permissions mentioned. Without annotations, the agent has no explicit read-only guarantee, but the description implies a non-destructive query.

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?

Three sentences, front-loaded with purpose. Every sentence adds value. No 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?

Given the simple functionality and presence of output schema, description sufficiently covers purpose, usage, and parameter behavior. No missing elements.

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?

Parameter 'venture' is fully described in schema (100% coverage). Description adds context about auto-detection and optional override, but no new semantic details beyond 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?

Clearly states it gets a quick summary of open ledger items, auto-detects venture, returns top 5 by priority. Distinguishes from sibling ledger tools (e.g., delimit_ledger_list, delimit_ledger_query) by focusing on context and priority.

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 says to use when wanting to know what to work on, implies context for AI. Does not explicitly state when not to use or compare to alternatives, but the purpose is clear.

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