imgui_app_status

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

No annotations are provided, so the description carries full behavioral burden. It states the tool reports 'binary path and availability' which adds some detail, and implies this is a read-only status operation. However, it doesn't state return format, whether it may block/wait, error behavior if not running, or whether the status reflects a local or remote process.

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?

Single, compact sentence that conveys purpose and key return contents without waste. It is appropriately sized for a zero-parameter status-check tool, though it could note the ready-state distinction without being verbose.

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-parameter status tool, the description is reasonably complete, but given no annotations and no output schema, it should clarify what 'status' includes (running/stopped states), whether the return differentiates binary-path-not-found, and any prerequisites. The description covers availability and path but leaves the status semantics somewhat vague.

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 has 0 parameters and schema coverage is 100%, so there is nothing for the description to add regarding parameters. Per the rubric, a 0-parameter tool gets a baseline of 4 since no parameter documentation 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?

The description uses a specific verb ('Check if... running') and identifies the resource (ImGui application) and return content (status, binary path, availability). It's clear among the many sibling tools, though it doesn't explicitly distinguish from imgui_get_state or imgui_drain_events which could overlap in checking application state.

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?

The description implies usage as a status/readiness check before performing ImGui operations, but provides no explicit when-to-use vs alternatives guidance. Among many sibling interaction tools, a reader must infer this is a pre-check diagnostic. No exclusions or alternatives are named.

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