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

With no annotations, the description carries the full burden and discloses non-obvious behavior: storage order is unspecified, it is not an atomic snapshot, and observedAt is inconsistent across event ages. It does not cover auth or rate limits, but it is strong for a read-only paginated tool.

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 front-loaded and free of filler, but the full Polish translation roughly doubles the length while adding no new information for a single-language agent. The content is well-structured yet not maximally concise.

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 simple two-parameter paginated read tool with no output schema, the description supplies enough context about ordering, atomicity, and observedAt availability to invoke it correctly. It does not describe the full return shape, but that is less critical here.

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 0%, so the description must compensate. It explains 'up to 50' as the page-size bound for the limit parameter and describes nextToken as an optional cursor, adding clear meaning beyond the bare integer/string types in the schema.

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 states a specific verb and resource: 'Read one bounded page of up to 50 PSI-FORUM ledger events, with an optional nextToken cursor.' It also distinguishes itself from a latest-events feed and an atomic snapshot, though it does not explicitly name sibling tools for routing.

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 signals when not to use the tool ('this is not a latest-events feed or atomic snapshot'), which is useful negative guidance. However, it does not state positive when-to-use conditions or name alternatives such as forum_search or forum_state.

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