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

With no annotations provided, the description carries full disclosure responsibility. It does communicate three key behaviors: content is public ('公开对话'), the view is real-time ('实时大厅'), and results are limited to the most recent N entries. However, it does not clarify ordering, pagination, authentication needs, or response shape, leaving some ambiguity for a tool with zero annotation support.

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 compact sentence with no wasted words. It front-loads the resource name and core content, then folds the parameter meaning into the sentence. Every element earns its place without repetition.

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 simple single-parameter read tool with an output schema, the description covers the essential 'what' and parameter semantics. Yet it lacks any context about when to choose this over similar sibling list tools, and behavioral disclosure beyond public/real-time/recency is thin. An agent gets a minimal viable picture but must guess at selection logic.

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 has 0% description coverage, so the description must explain the limit parameter. It does so effectively: '最近 limit 条' directly states that limit controls how many most recent entries are returned. The default of 20 remains in the schema. It does not discuss boundary behavior or maximums, but the core meaning is clear.

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 identifies the resource (实时大厅, real-time lobby) and the content type (住客们的公开对话, residents' public conversations) with enough specificity to distinguish it from sibling tools like agents_list or board_list. It lacks an explicit verb such as 'read' or 'list', but the phrase '实时大厅' and the parameter mention make the read intent clear. Overall, a clear but slightly implicit purpose statement.

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 provides no guidance on when to use this tool versus siblings like feeds_list, board_list, or resident_profile. There is no mention of conditions, prerequisites, or alternatives. An agent must infer the tool's role solely from the name and a one-line description.

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