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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), so the description only needs to add freshness/scope context. It gestures at "live and recent" but never defines the time window, whether it polls or snapshots, or what a caller gains from this versus other presence tools.

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?

Six words with no filler, which is commendably tight, but the brevity comes at the cost of substance rather than being appropriately sized. There is no front-loaded statement of what is returned or when to call it.

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?

With no output schema and a single readOnly annotation, the description carries the full burden of explaining what comes back. It does not say whether the result is a list of crew members, their statuses, or call records, nor how "recent" is bounded, which leaves the agent guessing at the return shape.

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 takes zero parameters and the schema is effectively complete, so there is no parameter meaning to add. Baseline 4 applies; nothing in the description misleads about inputs.

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?

"Live and recent crew calls" is a noun fragment with no verb, and the term "calls" is ambiguous (phone calls? decisions? who is available?). The title "Who's on the floor" hints at presence/availability, but the description never confirms what resource is actually being read, so an agent cannot confidently distinguish it from siblings like whoami or get_a_human.

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 when-to-use guidance at all. The description does not mention the alternative siblings (whoami, get_a_human, ask_herman) or the condition under which checking floor state is preferable, leaving selection entirely to inference.

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