cedulon_export_ledger

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

Annotations already declare readOnlyHint=true and openWorldHint=false, covering the safety and world-scope behavior. The description adds the useful detail that output matches npm run demo:export, but it does not disclose any other behavioral traits such as output size, asynchronous behavior, or prerequisites, so it only partially contributes beyond annotations.

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 a single, front-loaded sentence with no redundant words. It clearly communicates the operation, the target data, and the output format without padding.

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?

For a zero-parameter tool, the description is mostly sufficient: it names the data kinds and the output shape. It relies on familiarity with 'npm run demo:export' and leaves terms like 'checkpoint' and 'rail extract' undefined, but in a project context this is likely enough for an agent to invoke the tool correctly.

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?

The input schema has zero parameters and coverage is effectively 100%, so no parameter documentation is needed. The description's mention of the three export categories adds context about what the tool operates on, but since there are no configurable inputs, there is little parameter semantics to add.

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 names a specific verb ('Export') and the exact resources ('receipts, checkpoint, and rail extract'), making the tool's function immediately clear. It also distinguishes itself from siblings by being the export operation, as opposed to spend, audit, verify, or status actions. The reference to the demo:export JSON shape further pins down intent.

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 implies when to use this tool: any time an export of receipts, checkpoint, or rail extract data is needed in the demo:export shape. However, it does not explicitly mention alternatives or state when not to use it, leaving routing to siblings to be inferred rather than spelled out.

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