romm_socket

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

Annotations already declare destructiveHint=true, openWorldHint=true, and non-idempotent, so the safety profile is partly covered. The description does add value beyond annotations by disclosing the WRITES+TASKS permission requirement for sends and framing sessions as 'bounded'. It still omits what a send can destroy, session lifetime, and the bounded window (seconds/max_events) semantics.

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 clauses, front-loaded, with no filler. It is terse to the point of being cryptic, but nothing is wasted and the structural discipline is good.

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?

An output schema exists, so return values need not be described. But this is a multi-action lifecycle tool (catalog/open/send/listen/close) with 7 parameters and zero schema coverage, and the description neither maps actions to behavior nor ties them to the session_id/seconds/max_events controls. It is substantially incomplete for the tool's 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?

Schema description coverage is 0% and there are 7 parameters, so the description must carry the burden, but it explains none of them. event, payload, seconds, max_events, session_id and service are left entirely undocumented; only the action enum supplies any meaning. REALTIME/WRITES/TASKS are permissions, not parameters, so they do not compensate.

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 names a resource (realtime sessions) but pairs it with a vague dual verb ('Discover/use'), so an agent cannot tell whether this lists sessions, opens them, or both. It never references the action enum (catalog/open/send/listen/close) that actually defines what the tool does. The sibling set is a different domain so confusion is limited, but the purpose remains under-specified.

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?

'REALTIME enables connections; sends require WRITES+TASKS' gives a genuine prerequisite for the send path, implying usage conditions tied to permissions. However it gives no when-to-use-vs-alternatives guidance and no explanation of which action maps to which lifecycle step. Usage is only partially implied.

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