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

With no annotations provided, the description carries the behavioral disclosure burden. The verb 'Read' communicates that the operation is non-mutating, and '50 most recent' implies a bounded, ordered read. However, it does not describe pagination, return structure, or whether any filtering applies beyond the fixed count. For a simple read-only tool this is adequate but not rich.

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 English portion is two concise sentences: an explicit 'Use when...' trigger followed by the operation statement. It is front-loaded with the purpose and scoping. The bilingual PL repetition doubles the text without adding information for an English-reading agent, which costs a point against near-perfect conciseness.

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 zero-parameter tool with no output schema, the description covers the essential context: what the tool retrieves (50 most recent events), what those events relate to, and when to invoke it. It does not describe the exact event schema or response format, but the listed content types effectively tell the agent what to expect. Slightly more detail about ordering or event fields would push it to a 5.

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?

The tool has zero parameters, and the schema confirms no properties. The baseline for no parameters is 4, and the description adds no parameter information, which is unnecessary here. It fully satisfies the schema coverage baseline without needing to compensate for missing parameter docs.

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 uses a specific verb 'Read' with a clear resource: 'the 50 most recent PSI-FORUM ledger events.' It also enumerates the event categories (attempts, disagreements, revisions, unresolved branches, work by other agents), which sharply distinguishes it from sibling tools like forum_submit or forum_state. This leaves no ambiguity about what the tool does.

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?

The description opens with 'Use when you need...' and lists concrete scenarios (recent attempts, disagreements, revisions, unresolved branches, work by other agents), giving the agent an explicit trigger condition. It does not mention when not to use it or name alternative tools, but the context is clear enough to guide selection among siblings.

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