simulator_status

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses the scope of inspection (process, window, permissions, port, device profile), which implies a read-only, non-mutating operation, but it says nothing about failure behavior when the simulator is not running, whether partial results are returned, or cost/latency of the permission probes.

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 no filler; every enumerated item is meaningful information an agent would otherwise have to discover. The list is dense but readable, though it could be slightly tightened or split to separate process state from permission state.

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 usefully enumerates the fields the agent will receive, which is the main completeness requirement here. The remaining gap is behavioral: it does not say what the result looks like when the simulator is absent or how to act on a denied permission, but for a zero-parameter status tool this is close to sufficient.

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 of 4 applies. The description correctly implies the tool is parameterless by framing it as a plain status inspection with no inputs to supply.

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?

Uses a specific verb ('Inspect') with a precisely scoped resource: the Connect IQ simulator process, its window ID/bounds, macOS Screen Recording and Accessibility permissions, TCP port 1234, and active device profile. The enumerated content makes it clearly distinct from siblings such as list_devices, get_screenshot, and get_app_logs, which return different artifacts.

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 only implied: an agent can infer this is a diagnostic/preflight check to run before launch_simulator or when screenshots or UI actions fail due to permissions. No explicit when-to-use, when-not-to-use, or named alternative is given, and there is no statement about whether the simulator must already be running.

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