Check VCF Operations connection

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the bar is lower. The description adds real value by disclosing that the check actually performs a token acquire plus a design list call — i.e. it makes an authenticated remote request — and by naming what the response reports, which no structured field provides since there is no output schema.

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?

One dense sentence, front-loaded with the action and resource, with the payload of the check parenthesized. Nothing is redundant, though the parenthetical '(token acquire + MPB design list)' is slightly jargon-heavy for an agent unfamiliar with the internals.

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?

With zero parameters, no output schema and annotations already declaring safety, the description supplies the missing return-value summary and the nature of the underlying call. The only gap is failure behavior — whether a broken connection yields an error or a negative status report — which matters for a diagnostic tool.

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 the baseline is 4 and there is no parameter meaning to add or omit. The description correctly does not waste space restating an empty schema.

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 ('Checks') against a named resource ('the configured VCF Operations connection') and enumerates the reported fields (host, read-only mode, design count). It is clearly distinct from siblings like mpb_list_designs or mpb_test_source, though it does not explicitly name an alternative to contrast with.

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?

Usage is only implied: an agent can infer this is the connectivity/health probe to run before design or install operations. There is no explicit 'use this when...' statement, no mention of prerequisites, and no routing away from sibling tools such as mpb_install_status or mpb_get_design_status.

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