hpc_ai

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

No annotations are provided, so the description carries the full burden. It does disclose the four things the tool surfaces (address, token entry, model list, liveness), which is useful return-shape context, but it never states that it is read-only with no side effects, nor whether a token is required to call it.

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?

A single compact line with the concrete contents front-loaded and no filler. It is terse to the point of omitting an action verb, 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 tool with no output schema, the description should explain what the caller gets back and how to use it relative to hpc_chat. The enumerated sections partially cover the return values, but the relationship to the sibling chat tool and the auth flow remain unexplained.

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 the schema coverage is complete, so there is nothing for the description to compensate for. Baseline 4 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 names a concrete resource set — Westlake AI gateway (OpenAI-compatible), gateway address, token-claim entry, model list, liveness probe — so an agent can guess it returns gateway/endpoint metadata. But it is a bare noun list with no verb, and it never distinguishes itself from the sibling hpc_chat, which is the obvious confusable tool.

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?

There is no when-to-use guidance, no mention of prerequisites, and no routing to or away from the sibling hpc_chat. An agent must infer that this is the discovery/credentials tool rather than the chat tool.

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