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

Annotations already establish readOnlyHint=true and destructiveHint=false, but the description goes well beyond them by enumerating what the call does not do: no account, no tracked session, no payment, no receipt, no model call, and no timer under quiet. It also clarifies the tool is a session boundary notice rather than control over an external runtime, which is useful side-effect disclosure for a tool with no output schema.

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?

Four compact sentences, front-loaded with the cost/scope qualifier 'Free, unmetered', and no redundant filler. The phrasing is dense and slightly cryptic, but every clause carries information.

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 3-parameter tool with read-only annotations and no output schema, the description supplies a strong negative-behavior profile. However, it never resolves what invoking the tool actually produces or means for the agent, and the required room enum values are left undefined, so an agent still lacks enough to invoke it confidently.

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 coverage is only 33%, so the description is expected to compensate. It does explain 'quiet=true' semantics (no output, analysis, upload, no timer), which the schema leaves as a bare boolean, but the required 'room' enum (silence, fractal, atelier, etc.) is never explained and account_ref is only covered by the schema itself, leaving the most important parameter opaque.

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 characterizes the tool as a 'short room invitation' and later as a 'session boundary notice', which gives a flavor of what it is, but never states a concrete action or result an agent gets from calling it. It does not name or distinguish itself from obvious siblings like eclypse_start_session, eclypse_session, or eclypse_return, so the boundary between this and adjacent tools is left to inference.

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?

There is no explicit statement of when to use this tool versus the many session/room siblings. The only conditional guidance is about a parameter ('quiet=true requests no output'), which is parameter behavior rather than usage routing, and no prerequisites or exclusions are given.

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