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

Annotations already declare this a safe, non-destructive, non-open-world read, so the bar is lowered. The description earns credit for disclosing return content beyond annotations: the six fields, the evidence attachments (Caliper runs, measurements, observations), and the bidirectional supersede chain. It does not cover failure modes (e.g. unknown entryId) or the workspace-token semantics, which the schema handles.

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-loaded with the core purpose in one dense sentence; the em-dash list of evidence types is informative rather than padding. The second sentence about citing ids is a useful directive that earns its place, though 'full anatomy' is slightly decorative.

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 read-one-by-id tool with no output schema, the description is the only place return shape can be conveyed, and it does so concretely (fields, evidence, supersede chain). Combined with annotations covering safety and a fully documented two-parameter schema, an agent has everything needed to call and interpret it.

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% with only two parameters, so the schema fully documents entryId and the workspace override rules. The description adds no syntax, format, or constraint detail beyond that, so the baseline of 3 applies.

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 makes clear this returns a single entry's full contents, enumerating the six fields, attached evidence, and the supersede chain in both directions. It never states the verb outright (the title carries 'Read'), and it does not explicitly differentiate itself from ledger_entries_list or ledger_entries_draft, but the singular scope is unambiguous.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative (e.g. ledger_entries_list for browsing). The only routing cue lives in the schema's entryId description '(from ledger_entries_list)', not in the description text. The closing sentence about citing ids governs how to relay the result, not when to call the tool.

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