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

With no annotations, the description does useful work by disclosing that authentication is not required and that no browser automation is involved, plus an out-of-band fallback. It does not cover pagination, rate limits, or the shape of returned posts, which matters for a read tool with no output schema.

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 with zero filler: purpose first, then the recommended usage, then the fallback. Every sentence earns its place and the most important information is front-loaded.

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 one-optional-parameter read with no output schema, the description covers what it fetches, the auth posture, and a fallback path. The main remaining gap is any hint about the returned post fields or feed size behavior.

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 single 'limit' parameter is fully documented in the schema (100% coverage), so the schema carries the burden. The description adds nothing about defaults, ranges, or what happens when limit is omitted, so baseline 3 applies.

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: 'Read the unauthenticated public post feed', plus the notable constraint 'without browser automation'. It does not explicitly name how it differs from siblings like get_public_room_shard, so differentiation is implied rather than stated.

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?

'Preferred first read for public room state' gives an explicit ordering preference relative to other reads, and the HTTP fallback URL tells the agent what to do if the tool is unavailable. It stops short of naming a sibling to use instead when this is not the right choice.

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