delimit_ledger_add

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 does mention auto-detection of the venture, but it fails to state key behaviors such as whether the operation is idempotent, what happens on duplicates, permission requirements, or side effects. The description is too brief to fully inform an agent's decision.

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: two sentences that front-load the core action and immediately add useful context about auto-detection. Every sentence serves a purpose, and there is no redundancy or irrelevant information.

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?

The tool has 13 parameters, but only one is required, and an output schema exists. The description explains the basic purpose and auto-detection, but it fails to provide broader context about how items are organized (e.g., ledger types, prioritization impact) or what the tool's response looks like. Given the output schema, it is minimally complete but could be improved.

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 baseline is 3. The description adds value by explaining the auto-detection of the 'venture' parameter and the purpose of the ledger ('tracks what needs to be done across sessions'). However, it does not elaborate on other parameters like 'item_type', 'priority', or 'tags', relying on the schema. This is acceptable but not exceptional.

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 action ('Add a new item to a project's ledger') and the resource ('ledger'). The verb 'Add' is specific, and the tool differentiate from siblings like 'ledger_update' or 'ledger_list' by focusing on creation. The purpose is unambiguous.

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 context for when to use the tool (adding items to a project's ledger) and notes auto-detection of the venture. However, it lacks explicit guidance on when not to use it or comparisons to alternative ledger tools like 'delimit_ledger_propose' or 'delimit_ledger_update'. The usage is clear but not exhaustive.

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