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

Annotations only declare mutation-safety (readOnly=false, destructive=false, openWorld=true). The description adds genuinely useful behavioral detail beyond them: idempotency via dedupe on overlapping ranges, size-limit feedback ('a run that fills up says so'), the single-point outcome for non-series sources, and a `needs_confirmation` return that ties to the approvalId param. This is well above what the annotations convey.

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?

Front-loads the purpose, then layers usage, constraints, and re-run safety. Mostly efficient, though the 'worth far more than one that begins today' pitch is mildly promotional filler that could be trimmed.

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?

No output schema exists, and the description compensates by disclosing the re-run/dedupe behavior, the range-size limitation, and the `needs_confirmation` outcome. Combined with the annotations, an agent has enough to call and interpret it, though nothing confirms what a successful backfill returns.

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 80%, so the schema already documents id/from/to/workspace. The description implies the from-range concept and hints that approval/confirmation is involved (linked to approvalId), but adds no format or semantics beyond the schema. Baseline 3 is appropriate at this coverage level.

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?

States a specific action: run the frozen feed instruction over a past range to populate history. The verb+resource ('run' + 'frozen instruction'/'range') is concrete. It does not name the closely related sibling ledger_feeds_run, so it stops short of a 5.

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?

Gives a clear condition for invoking: 'Offer this whenever you create a feed,' with a rationale (a chart with history is more valuable, expectations can be judged). It does not explicitly distinguish when to use this versus ledger_feeds_run or ledger_feeds_preview, so no exclusions are covered.

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