Verify the ContextMint Bridge connection end-to-end

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

Annotations declare readOnly/idempotent/openWorld, and the description adds substantial context beyond them: no auth required, and a precise enumeration of the diagnostic fields returned (role, port, version, extension link state, elapsed time) plus the plain-English hint categories.

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 opening sentence followed by two short, high-value ones. The field enumeration is long but every item is meaningful for interpreting the diagnostic output; 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?

With no output schema, the description carries the return-value burden and does so by naming each diagnostic field and explaining the failure-mode hints. Nothing an agent needs to interpret or route to this tool is missing.

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?

Zero parameters, so the schema imposes no semantic burden and the baseline is 4. The description does not need to explain inputs, and it correctly does not.

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?

States a specific action (round-trips a small public URL through ContextMint Bridge) and the resource (bridge connection diagnostics). It is unmistakably distinct from the data-retrieval siblings like hemnet_search_listings, being an end-to-end connectivity check.

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?

Gives an explicit trigger: 'Call this when a real tool fails and you want to know which hop broke.' It does not state when not to use it, but the diagnostic framing makes that clear enough in context.

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