delimit_ledger_propose

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

The description explains it analyzes repo state, sensing signals, and completed work to suggest items with rationale, implying read-only behavior. However, no explicit statement about non-destructive nature, and no annotations provided, so the burden is on the description, which is mostly met but could be clearer.

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?

Four sentences with clear first-sentence purpose and usage timing. The last sentence 'Works across all AI models via MCP' is somewhat extraneous but not harmful.

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 presence of an output schema and full parameter documentation, the description covers purpose, usage timing, and high-level behavior. Missing details like prerequisites or error conditions, but overall adequate for a suggestion 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?

Input schema has 100% coverage with descriptions for all three parameters. The description does not add significant extra meaning beyond what the schema already provides, meeting the baseline expectation.

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 'Propose new ledger items' with a specific verb and resource, and distinguishes from siblings like delimit_ledger_add (direct addition) by explaining it suggests items based on analysis.

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?

Explicit guidance to run at end of build loops or when queue is empty provides clear context for use, but no comparison to alternatives or when to avoid use.

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