List connected Roblox clients

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuine value by disclosing that it reports which client the current session resolves to, plus produces=bounded-candidates; the phase/cost/idempotency tail partly restates the annotations rather than extending them.

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 purpose and when-to-use guidance are front-loaded and efficient. The trailing 'Signature/Phase/Requires/Safety' block is largely boilerplate that partly duplicates the annotations, so it does not fully earn its space.

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, the description carries the burden of explaining return content, and it does so by naming the returned fields and the bounded-candidates output. For a zero-param read tool this is essentially complete, though pagination or result-size limits are not addressed.

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, so the baseline is 4 and the description has no parameter semantics to describe. There is nothing the schema leaves ambiguous that the description needs to compensate for.

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?

States a specific verb and resource ('List every connected Roblox executor client') and enumerates the returned fields (clientId, account, place, executor). It is clearly distinguishable from select-client, which changes the selection rather than enumerating clients.

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?

Explicitly says when to call it: 'before select-client when more than one client is connected or the target is unknown.' It names the alternative tool and the exact triggering condition, leaving nothing to inference.

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