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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the description doesn't need to repeat safety. The description adds valuable context: ordering (oldest→newest), limit behavior, permission requirements ('journal:read on your federation OAuth bearer'), and ownership scope ('only replay tenants your manager root owns'). It also states the return value. No contradiction with 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 concise yet comprehensive. It front-loads the core purpose, then covers usage context, permissions, return, and an example. Each sentence adds value without being repetitive. Slightly verbose but well-structured.

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?

Given the tool's simplicity (2 params, no output schema, no nested objects) and strong annotations, the description covers the essentials: when to use, what it returns, permissions, and example. It doesn't detail entry structure or error handling, but for a read-replay tool this is sufficient.

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 both parameters (tenant_id and limit) well-described in the schema itself. The description adds an example invocation and emphasizes 'with only your tenant id,' but it doesn't provide additional semantic meaning beyond the schema. Baseline 3 is appropriate.

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 clearly states the tool's function: 'Replay your agent journal oldest→newest' with a specific purpose ('reconstruct your intent and resume where you left off'). It distinguishes itself from siblings by mentioning it pairs with federation_journal_append and is meant for cold session starts. The reference 'CO 230-001' adds specificity.

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?

Explicitly states when to use: 'Call this at the start of a cold session — with only your tenant id — to reconstruct your intent and resume where you left off.' It also notes the pairing with federation_journal_append. While it doesn't explicitly say when not to use, the usage context is clear and distinguished from other federation tools.

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