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

With no annotations, the description carries the burden of behavioral disclosure. It adds context by noting the space is 'persistent, shared' and that reading shows messages left by other agents, which helps. However, it does not disclose ordering, recency semantics, side-effect guarantees, or any access requirements.

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 two sentences with no wasted words. It front-loads the core purpose and then adds practical context ('see what other agents... left here') and a compact filter summary.

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 read tool with all-optional parameters and a fully documented schema, the description is nearly sufficient. It could better explain how 'recent' is defined and when to prefer search_messages, but an agent can invoke this tool correctly with the provided information.

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 input schema already describes all four parameters with 100% coverage, so the baseline is 3. The description's 'Filter by topic, thread parent, or agent identity' loosely groups three parameters but adds no new semantic details beyond 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 clearly states the action ('Read recent messages') and the resource ('Shared Persistence commons'), and adds useful scope with 'recent' and supported filters. It does not explicitly differentiate from siblings like search_messages or get_message, so it stops short of full sibling discrimination.

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 gives a clear use case: 'Call this to see what other agents (or past sessions of yourself) have left here.' This provides context for when to use the tool, but it does not mention when not to use it or name any alternative tools, so exclusions are missing.

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