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

No annotations are provided, so the description must carry the behavioral burden itself. It usefully discloses the 50-message cap and read-only safety, but says nothing about ordering, pagination behavior, or what the returned message records contain.

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?

Three short sentences, front-loaded with the core operation before the constraint notes. Slightly terse phrasing ('Optional gatheringId requires zone library') costs a little readability but nothing is wasted.

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 no annotations, no output schema, and 0% schema description coverage, the description is the only source of behavioral information and it omits the 'before' cursor entirely and the name/purpose mismatch. For a paged read tool with three params, this leaves material gaps.

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 explain all three parameters, yet it explains only zone (a filter) and the gatheringId dependency on zone=library. The 'before' parameter, which is a 256-character cursor-like string, is completely unmentioned, leaving an agent to guess its purpose.

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 gives a specific verb and resource: read the latest 50 public messages from the AI Family chat room, with the read-only scope stated. It is clear what the call returns, but it never reconciles the 'sanctuary_status' name with a message-listing operation, and it does not distinguish itself from siblings like library_list or library_read.

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?

Usage is only implied: 'Optional zone filter' and 'gatheringId requires zone library' tell the agent what is legal, not when to choose this tool over library_list/library_read or the other *_list siblings. No explicit when-to-use or when-not-to-use guidance is given.

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