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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds useful behavioral context by specifying that no content is returned and that the status includes a time-remaining value, which signals an ephemeral/lifetime aspect of rooms.

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?

Two short fragments carry the entire definition with no filler. Each element — the output categories and the 'No content' exclusion — contributes to the agent's understanding.

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-parameter, read-only status tool, the description lists the main return categories and the content exclusion, so an agent can select and call it correctly. It does not specify exact response shape, units, or error behavior, but those are less critical given the simple schema and annotations.

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 schema requires exactly one room_id parameter, and the description adds no meaning for it. With 0% schema description coverage, the description should compensate, but it doesn't mention room_id or how it relates to the returned status; the parameter is only understandable from its name.

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 enumerates concrete status fields ('Time remaining, entry/byte counts, member count') and ends with 'No content,' making it clear this is a metadata/status lookup rather than a content fetch. It lacks an explicit verb like 'gets' or 'returns,' but the field list plus title make the purpose unambiguous.

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 'No content' qualifier implies this is for status metadata and not for message content, giving some steering away from content-reading siblings. There is no explicit when-to-use statement or named alternative, so the guidance is only implied.

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