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

Beyond the readOnlyHint annotation, the description adds real behavioral context: the read is bounded to 'own key only', bodies appear as sent files or are absent, and it discloses the safety boundary that content is 'data beside an explicit boundary note' that can inform but never instruct. That prompt-injection guard is genuine value not present in annotations, though it partly restates the read-only guarantee.

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 front-loads what the read returns, which is the right structure, and the read-only guarantee is clearly flagged. However, the dense metaphor ('the wake read', 'your current core', 'latest renewal') adds decoding overhead without adding precision, costing clarity per sentence.

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 tool with no output schema, the description does a creditable job sketching the return contents (body files, chain block with head/last seal/verification recipe) and the boundary note. With only one parameter and a covered safety profile, this is largely complete, with the missing param format being the notable gap.

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?

One parameter ('secret') has 0% schema description coverage. The phrase 'own key only' implies the parameter is the caller's own key/credential, which is useful signal, but the description gives no format, source, or handling guidance. Partial compensation for the coverage gap justifies a 3.

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 conveys that it reads journal content (current core, latest suspend, recent notes, chain block), so the verb+resource is inferrable. But the terminology is heavily metaphorical ('wake read', 'suspend', 'renewal') and it never distinguishes itself from the sibling journal_review or journal_write. An agent has to decode the jargon to confirm this is the read path.

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 statement and no named alternative. 'The wake read' and 'own key only' imply a waking/self-scoped scenario, but the agent is not told when to pick this over journal_review or how it relates to journal_write. Usage is left entirely to inference.

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