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

With no annotations provided, the description carries the behavioral transparency burden. It explicitly uses 'Read', implying a non-mutating operation, and qualifies the data as 'disclosed', setting expectations about scope. The caveat about roster membership not being scientific authority also prevents misinterpretation of the returned data.

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 short sentences with no filler. The main purpose is front-loaded in the first sentence, and the second sentence adds a meaningful caveat without redundancy.

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 zero-parameter read tool with no output schema, the description sufficiently conveys what the agent will learn: scientist surfaces and automatic wake capability. It also provides the key interpretive caution. The term 'surfaces' is slightly vague, but in context it reads as a domain-specific concept and does not leave the agent without enough to call the tool correctly.

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 tool has zero parameters, and the schema covers 100% of the (empty) parameter surface accordingly. The description does not need to explain parameters, so the baseline of 4 applies. No parameter semantics are missing.

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 opens with the verb 'Read' and identifies the resource: the disclosed CrystalRAM scientist surfaces. It also specifies the additional detail of whether each runtime can wake automatically, which clearly distinguishes this roster tool from the sibling tools that handle sessions, dispatches, or inboxes.

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 gives clear context for when to use the tool: when roster membership and wake capability are needed. It also adds an interpretive guideline—'Roster membership is not scientific authority'—which helps the agent avoid misusing the data. It does not explicitly name alternative tools or exclusion criteria, so it stops short of a 5.

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