check_qiaotong_connection

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

Annotations are all false and provide no safety profile, so the description carries the full burden, and it delivers: it discloses the strict version-pinning behavior of qtmodel and the non-obvious Windows HTTP.sys gotcha that the URL host must be `localhost` rather than `127.0.0.1` through a port forward. This is precisely the kind of platform-specific behavior an agent could never infer from the schema or annotations. No contradiction with the annotations.

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?

Well-structured and front-loaded: purpose → trigger condition → three statuses with fixes → return values → critical gotcha, with every section earning its place. Mild deduction because the inline Chinese translations roughly double the length, though they are arguably necessary for this user base.

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 0-parameter diagnostic tool with no output schema, nothing an agent needs to invoke correctly is missing: the trigger condition, all three possible statuses with per-status remediation, the return contract, and the port-forward host pitfall are all specified. The description fully substitutes for the absent 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?

With 0 parameters, the schema documents everything there is to document, so the baseline is 4. The description adds value by compensating for the missing output schema, naming the four returned components (status, human-readable message, recommended action, client/server versions) and the exact status enum values.

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 verb and resource ('Diagnose the connection to QiaoTong software') and enumerates the three distinct outcomes (connected, version_mismatch, software_not_running), which makes the tool's scope unmistakable. Among ~150 modeling-focused siblings, it is the only connection diagnostic, so an agent can immediately tell it apart.

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, imperative trigger condition — 'CALL THIS FIRST when any tool reports the backend is unavailable' — which is exactly the routing decision an agent faces. It also tells the agent what to do after each outcome (upgrade QiaoTong, start the software and wait), effectively supplying the post-call action plan alongside the when-to-call rule.

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