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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false. The description adds useful behavior beyond the annotations, notably that it does not move the unread cursor and that default results include superseded entries and event history; it does not detail output formatting, but that burden is lower with annotations present.

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 front-loaded and dense: it states purpose, default/current behavior, sibling routing, and the unread-cursor side effect without padding. The minor restatement of status/type filtering is acceptable and does not undermine efficiency.

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?

With three optional parameters, full schema coverage, rich annotations, and no output schema, the description supplies everything needed to call the tool correctly: purpose, filtering modes, alternatives, and side effects. No material gap remains for an agent selecting or invoking 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%, so the baseline is 3. The description adds meaningful semantics beyond the schema by clarifying what the default false behavior returns and describing current=true as a complete snapshot of what is in force now.

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?

States a specific verb and resource: reading this Space's Articles, defined as the register of proposed and ratified decisions numbered A1, A2, etc. It also distinguishes the tool from read_pointer and space_state, so an agent can identify its role without opening the schema.

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 explains the default behavior of returning full history including superseded entries and events, versus current=true for an in-force snapshot. It names the alternatives and their conditions: read_pointer for one entry and its discussion, space_state for the last 10 ratified.

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