connect_houdini

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

With no annotations, the description carries the full burden. The phrase "from now on" usefully discloses that this is a persistent state change affecting subsequent calls, but nothing is said about failure modes (invalid/absent port), whether existing sessions are dropped, or auth needs.

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?

The purpose sentence is front-loaded and terse, and the pointer to get_houdini_connection_status is efficiently placed. The Args block is slightly redundant with schema but short, so little 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 simple single-parameter connection tool with no output schema this is nearly adequate — it says what it does and how to find a port. It still omits what the agent should expect afterward and error/edge behavior, leaving a gap for a state-changing connection tool with no annotations.

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?

Schema description coverage is 0%, so the description must compensate. The Args line clarifies that the port identifies a specific Houdini session and points to get_houdini_connection_status as the way to obtain it, which adds real meaning, though it does not state valid ranges or format.

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 states a clear action on a specific resource — connect to ("talk to") the Houdini instance on a given port — and the phrase "from now on" signals this changes the active session. It does not name sibling tools start_houdini/stop_houdini, but the purpose is readily distinguishable from them.

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?

"get_houdini_connection_status lists the sessions and their ports" implicitly tells the agent to discover a port there before calling. However, there is no explicit when-to-use versus when-not, no description of relationship to start_houdini, and no prerequisites stated beyond that hint.

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