get_houdini_connection_status

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

No annotations exist, so the description carries the full burden and does so well: it discloses the non-raising behavior ('without raising on disconnect') and enumerates the return payload (bridge URL, health payload, per-session port/pid/version with the current one marked). It does not state auth/permission requirements, but for a pure status probe that is minor.

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-loads the key behavioral fact ('without raising on disconnect') and keeps the rest to two tight sentences. The enumeration of return fields and the sibling routing are dense but each clause earns its place; slightly verbose rather than wasteful.

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 annotations and no output schema, the description fully compensates by describing both the failure semantics and the exact shape of the returned diagnostics. Nothing an agent needs in order to call this correctly 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?

The tool takes zero parameters, so there is nothing to disambiguate and the schema is empty. Baseline for 0 params is 4; the description adds nothing further here because none is needed.

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+resource (check the MCP-to-Houdini bridge / connection status) and explicitly separates itself from the neighbouring lifecycle siblings: 'connect_houdini switches; start_houdini starts one.' An agent can tell instantly that this is the read-only diagnostic, not a mutator.

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 clear context ('Use this before live viewport workflows when Houdini may have restarted') and names the alternatives connect_houdini and start_houdini with their roles. It does not spell out an explicit when-not-to-use condition, so it stops short of a 5.

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