Connection status

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds real context by disclosing that the response may include instructions for the user to connect, which is behavior not captured by annotations. It stops short of describing the return shape or what happens when the connection is absent.

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?

Two short sentences with no filler, and the core question (connected or not) is front-loaded. The sequencing directive sits at the end where it is slightly less prominent than it could be, but nothing is wasted.

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 read-only probe with no output schema, the description covers what is checked and what the agent may learn when the check fails. The only gap is that the exact returned representation is not characterized, which matters slightly given there is no output schema.

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 there is nothing for the schema to document and no semantic burden to carry. Baseline applies.

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 states a specific resource and scope: whether the MIB2 Configurator page is connected, plus remediation guidance when it is not. It is distinguishable from most siblings, though the nearby 'get_state' tool could plausibly be confused with it since no explicit contrast is drawn.

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?

'Call this first' is an explicit and unusually strong ordering directive that tells the agent when to reach for this tool relative to everything else. What is missing is any when-not condition or named alternative for the non-connected case.

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