check_abaqus_connection

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

No annotations are provided, so the description alone must convey behavioral traits. It reveals only that the result is a concise human-readable status; it does not say whether the check mutates anything, what failure modes exist, whether a timeout causes errors, or what statuses can be returned. Behavior is largely undisclosed.

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 short sentence states the core behavior and output style with no filler, and the key information is front-loaded. For a simple health-check tool this is an efficient length.

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?

The tool is simple, has no required parameters, and an output schema exists, so the description does not need to explain return values. However, it omits usage context and timeout semantics, and the ambiguity with 'ping' is unresolved, leaving the definition minimally adequate rather than complete.

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 schema has 0% description coverage and the description says nothing about the 'timeout' parameter, its units, or the meaning of null/default. The parameter is optional and self-named, which softens the gap, but the description does not compensate for the missing schema documentation.

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 clearly states the operation ('Return') and the resource ('bridge status'), and it adds a useful output-shape cue ('concise human-readable'). It does not explicitly differentiate itself from the sibling 'ping', which likely serves a very similar purpose, so the tool name must carry that distinction.

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 statement about when to use this tool, when not to, or which alternative to prefer. With 'ping' and diagnostic tools like 'diagnose_job' and 'check_silent_failures' in the toolset, the agent is left to infer the intended use from the name alone.

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