Connection status

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the description needn't repeat it. However, with no output schema present, the description carries the full burden of describing the return shape and it does not — an agent cannot tell whether a disconnected state is reported as a boolean, a status string, or an error, nor whether the check is passive or triggers a reconnect attempt.

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?

A single front-loaded sentence with zero filler, appropriately sized for a parameterless status check.

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-input, read-only probe, the description covers what the tool does but not what an agent gets back or how to interpret it, and there is no output schema to compensate. That return-value gap is the one thing an agent needs to act on the result.

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 there is nothing to disambiguate and the baseline of 4 applies. The description correctly implies no input is needed.

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 ('Report') and a specific resource ('whether the simulator page is connected to this MCP server'), so an agent knows exactly what the call answers. No sibling tool performs a connectivity check, so differentiation is implicit rather than stated, and 'connected' is left undefined (WebSocket open? page loaded? responding to pings?).

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?

Usage is implied by the purpose: check link health before or after driving the simulator. There is no explicit guidance on when to call it versus alternatives such as open_simulator (which presumably establishes the connection) or how to act on a negative result, leaving the agent to infer the diagnostic workflow.

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