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

With no annotations, the description carries the full behavioral burden. It does disclose the ordering of results (newest first), which is genuinely useful, but says nothing about pagination behavior, permissions, whether reading affects read state, or what errors look like.

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?

A single short sentence that puts the resource first and the ordering second, with no wasted words. Its brevity is efficient, though it borders on under-specification given the undocumented parameters.

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?

No annotations, no output schema, and no parameter documentation means the description is the only source of guidance — yet it omits pagination semantics, identifier format, and return shape. For a paginated read tool with three free-form parameters, this is not complete enough.

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% for three parameters. The description is silent on the room identifier format, the default/meaning of limit, and whether since is a timestamp or message id; "newest first" is only a faint hint about how since/limit paginate. It does little to compensate for the coverage gap.

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 a room") plus an ordering trait ("newest first"), so the basic operation is identifiable. However, it never clarifies what a room is in this system or how it relates to the write counterpart haven_room_post, leaving sibling differentiation to inference.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative tool is named. The presence of haven_room_post implies a read/write split, but the agent must infer that this is the retrieval counterpart rather than being told.

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