model_status

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

No annotations are provided, so the description carries the burden; it does convey that this is a state check reporting connection status and the tracked model, which implies a non-mutating query. However, it does not say whether calling it has side effects such as attaching to or opening a session, nor anything about failure modes if no session 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 tight sentence with no filler, and the core purpose is front-loaded. It is efficient, though its brevity contributes to the documentation gaps elsewhere.

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, and the sentence partially covers the return content (connection status plus tracked model), which is helpful. For a two-parameter tool with zero schema documentation and no annotations, however, the definition leaves parameters and any session-resolution behavior unexplained.

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?

Schema coverage is 0% and the description never mentions work_dir or model_root, so neither parameter's meaning (a working directory? a model search root? how they affect which session is inspected) is explained anywhere. The only hint is 'which model it tracks', which is too vague to disambiguate model_root usage.

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 names a specific verb and result ('Report whether a model session is connected and which model it tracks'), which is more than a restatement of the name model_status. It is reasonably distinguishable from sibling simulation_status in that it speaks about a model session rather than a simulation, though the distinction is implied rather than stated.

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?

There is no explicit guidance on when to call this versus model_open, simulation_status, or the model_* object tools, and no prerequisites or ordering advice (e.g. call after model_open). The agent must infer the diagnostic use case from the wording alone.

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