Foreground control status

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

Annotations already establish the safe read-only, non-destructive, closed-world profile, so the burden is lighter. The description adds the payload contents (owner, task, pause state, heartbeat expiry), which is useful behavioral context, but says nothing about staleness, expiry semantics, or what happens when no owner exists.

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 that enumerates the returned fields with zero filler. Nothing is repeated or padded.

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?

There is no output schema, so the enumeration of returned fields is genuinely valuable, but the description does not compensate for the total absence of parameter documentation or the device-targeting behavior. Adequate but with clear gaps for a status tool whose main question is which device to query.

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?

Two parameters with 0% schema description coverage, and the description adds no meaning for deviceId or deviceName — not even whether they are optional or mutually exclusive. With no params the baseline would be 4; here the description leaves the selection of device entirely unexplained.

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 ('Return') plus resource ('foreground-control owner, task, pause state and heartbeat expiry'), so an agent knows exactly what is being read. It does not explicitly distinguish itself from the sibling family (foreground_control_acquire/heartbeat/pause/release), though the name and phrasing make it obviously the read-only counterpart.

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?

No guidance on when to call this versus foreground_control_acquire, foreground_control_pause, or foreground_control_release, and no stated prerequisites or exclusions. The sibling names hint at a state-machine workflow, but the description never tells the agent where this read fits in it.

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