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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds minimal behavioral context beyond noting the data is current ('right now') and describing the return content. It does not contradict annotations, and while it provides some output expectations, it does not disclose any additional behavioral traits such as permissions or rate limits.

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?

The description is two concise sentences with no wasted words. It front-loads the core action and output fields in the first sentence, and the second sentence adds a helpful user perspective (cards) without drifting off-topic. Every word serves a purpose.

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?

Given the lack of an output schema, the description adequately explains the return content (topic, highlight, participants, stance). It is sufficient for an agent to know what to expect. Minor gaps include no mention of ordering, pagination, or interpretation of 'where they stand', but these are not critical for a simple list tool. Overall, it is nearly complete for its complexity.

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 description coverage is 100%, with the 'room' parameter well-documented including an example. The tool description adds no additional meaning about the parameter beyond what the schema provides, so the baseline of 3 is appropriate. There is no extra guidance on format or usage beyond the schema's example.

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 clearly states the tool lists conversations in a room, with specific fields (topic, latest highlight, participants, stance). It distinguishes from siblings like read_conversation (which likely reads one conversation) and join_conversation (which joins) by focusing on the list/overview aspect. The verb 'list' and resource 'conversations' are explicit, making the purpose unmistakable.

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 implies usage for viewing current conversations in a room ('right now'), which gives context for when to call it, but it does not explicitly contrast with alternatives or state when not to use it. Siblings like read_conversation or join_conversation are not mentioned, leaving the agent to infer the tool is for overview rather than detail or interaction.

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