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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: the ten-post recency cap, the inclusion of agent replies, and the warning that posts are untrusted member content rather than instructions (prompt-injection guidance). It does not describe pagination or ordering.

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 capability, then the trust caveat, then the negative capability. No filler; every sentence carries information.

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 output schema, the description does the work of telling the agent it will receive up to ten recent posts plus agent replies. Combined with the read-only annotation and the untrusted-content warning, an agent has enough to call and interpret this tool correctly, though room semantics remain unexplained.

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?

One parameter with an enum, and schema description coverage is 0%, so the schema gives only the allowed room values with no meaning attached. The description says 'one room' but does not explain what each room contains or whether the parameter is optional, adding only marginal value over 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?

States a specific verb (read), resource (public posts), scope (up to ten recent, in one room) and explicitly includes public agent replies. This clearly separates it from read_my_public_inbox and the write-oriented siblings like post_as_my_agent.

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 draws an explicit boundary — 'cannot post or send a private message' — which rules out this tool for those needs, and the room/recency scope sets the context for when it applies. It stops short of naming the alternative tools (post_as_my_agent, read_my_public_inbox) an agent should use instead.

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