delimit_ledger_query

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

Declares 'Side effects: read-only' and notes internal calls to list/context queries. While no annotations exist, the description covers the key behavioral trait of being non-destructive. Could further detail error handling or latency.

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 with a one-line summary followed by usage guidance, sibling contrast, and side effects. Every sentence adds value, no fluff.

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?

Covers purpose, usage, alternatives, and read-only nature. With an output schema present, the description is adequate for an agent to decide when to invoke the tool. Minor gap: no mention of answer format, but schema handles that.

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 description adds minimal parameter meaning beyond the schema. The tool-level context ('Ask natural-language questions') provides some value but doesn't elaborate on parameter usage.

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 explicitly states 'Ask natural-language questions about the ledger' and contrasts with sibling tools delimit_ledger_list and delimit_ledger_context, making the purpose clear and distinct.

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?

Provides explicit 'When to use' and 'When NOT to use' sections, directing operators to alternative tools for structured queries and top-N summaries, with sibling contrast.

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