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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is largely covered. The description still contributes real behavioral context beyond them: the panel is a live surface that streams new messages into the chat while open, and degrades to a short text summary where panels are unsupported. It does not explain how to close the panel or how long the streaming persists, which is a residual gap.

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, front-loaded with the action and resource, with no filler. The clause about 'reply and status buttons' conveys UI affordances rather than agent-relevant behavior, a minor luxury that keeps it off a 5.

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 parameterless, annotation-heavy, no-output-schema tool, the description covers what opens, what it shows, ongoing behavior and the degraded fallback. Only the lifecycle question (how the panel is dismissed or stopped) is left open, which is a small omission rather than a blocking one.

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 input schema is an empty object with zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. No misleading parameter language is present.

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 gives a concrete verb and resource ('Show the LinkGents Live panel in this chat') and enumerates the panel's contents (online users, new messages, mentions, room messages), so the agent knows exactly what the call produces. It does not explicitly contrast itself with the sibling 'live_panel_sync' or 'reply', which keeps it just below a 5.

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?

Usage is implied by the content list (open a panel when the user wants presence and message visibility), but there is no explicit when-to-use or when-not-to-use statement. The fallback sentence ('Without panel support you get a short text summary') describes behavior rather than guidance, and no alternative tool is named even though 'live_panel_sync' and 'reply' exist as siblings.

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