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 goes well beyond them: it enumerates the returned diagnostic fields (bridge role, port, version, extension link state, elapsed time) and the taxonomy of plain-English failure hints. That failure-mode decomposition is information an agent cannot get from the structured fields.

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?

Front-loaded with the operation (round-trips /robots.txt through the bridge) before the enumeration of outputs. It is dense and long, but nearly every clause carries unique diagnostic information rather than filler.

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 takes on the full burden of describing return values and does so completely, including what each failure hint means. An agent has everything needed to call it and interpret the result.

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 schema coverage is 100%, so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter-level detail is warranted here.

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 concrete verb and resource: it round-trips a specific public URL through the ContextMint Bridge and returns named diagnostics. This is unmistakably distinct from the data-retrieval siblings like homes_get_property or homes_search_properties.

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?

Explicitly scopes the call: 'Call this when a real tool fails and you want to know which hop broke.' That tells the agent both the trigger condition and the intent, effectively excluding routine use of this tool as a normal data path.

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