delimit_ledger

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

No annotations provided, so the description carries full burden. It states 'read-only' and 'Calls backends.gateway_core.query_ledger,' which is good. It also mentions integrity verification. However, it does not cover potential rate limits or authorization requirements, leaving some gaps.

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?

Well-structured: main purpose first, then usage guidelines, sibling contrast, and side effects. No unnecessary words; every sentence adds value.

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 complexity and presence of an output schema, the description covers all needed aspects: purpose, usage boundaries, side effects, parameter hints, and integrity check. It is complete for a query 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%, so baseline 3. The description adds little beyond the schema; it mentions 'filter by API name' and integrity verification related to validate_chain. The added value is minimal, hence a 3.

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 that this tool queries the append-only contract ledger (hash-chained JSONL). It differentiates from sibling tools like delimit_ledger_list (reads work items) and delimit_audit (reads audit logs), making its purpose 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?

Explicitly states when to use (read/audit contract ledger) and when NOT to use (project work ledger, use delimit_ledger_list/query). Also provides sibling contrast, helping the agent choose correctly.

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