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

Annotations already mark this as a non-read, non-destructive, closed-world write, so the description adds context beyond that: it discloses the conflict failure on superseded entries and that the call may return a needs_confirmation envelope. It does not spell out auth/permission requirements or idempotency, but for an annotated mutation tool this is solid behavioral disclosure.

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?

It is front-loaded with the core action and each following sentence earns its place (routing to the metric-reading sibling, settlement rationale, conflict failure, id source, confirmation). It is dense and slightly long, but no sentence is filler.

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?

With no output schema, the description carries the return-behavior burden and does reasonably: it discloses the conflict failure and the possible needs_confirmation response (which ties to the approvalId parameter). Combined with full schema coverage and annotations, an agent has enough to call it correctly, though a fuller picture of the confirmation flow would be ideal.

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 description coverage is 100%, so the schema already documents every field including the kind enum defaults. The description still adds value by clarifying the provenance of entryId ('ids come from ledger_entries_list') and by grounding summary/kind usage in examples, which is slightly above the baseline-3 that pure schema coverage would justify.

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 precise verb and resource (records/attaches evidence against an open Ledger entry) and enumerates the concrete forms evidence takes (manual observation, implementation note, Caliper run reference). It explicitly separates itself from the metric-reading path by naming ledger_metrics_record_reading, so an agent can route correctly without opening sibling schemas.

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?

It states when to attach ('attach it as it arrives'), why ('evidence is what settlement later reads'), and an explicit when-not plus alternative ('metric readings attach themselves via ledger_metrics_record_reading — don't duplicate them here'). It also notes the conflict failure on superseded entries and that ids come from ledger_entries_list, leaving little to inference.

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