opn_overview

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 helpfully discloses that the response includes 'whether writes are enabled' (a config-state flag likely relevant before any mutation), but it never explicitly states that this call itself is read-only and side-effect free, nor does it mention permissions or cost.

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 sentence, front-loaded with the returned contents and ending with the one non-obvious flag (writes enabled). No filler, no restatement of the tool name.

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 no-argument status tool with an output schema that already documents the return shape, the description covers the essential scope. The only missing piece is an explicit statement that the call is read-only, which matters given the absence of annotations.

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, and the description correctly adds no parameter guidance. Baseline of 4 applies since there is nothing further the description could clarify about inputs.

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 enumerates exactly what the tool returns (version, update status, interfaces, gateways, services) and the 'in one call' phrasing signals an aggregated snapshot, distinct from the narrower siblings like opn_service and opn_items. It lacks an explicit verb (e.g., 'returns'/'summarizes') and never names a sibling it supersedes, so differentiation is inferred 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?

The 'in one call' framing implies this is the cheap orientation call to make before drilling into opn_items, opn_service or opn_settings, but no when-to-use or when-not-to-use condition is stated. An agent must infer that this is a broad snapshot tool rather than a targeted query.

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