Connect Houdini Engine bridge

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

Annotations already declare readOnlyHint=false, openWorldHint=true, destructiveHint=false, so no contradiction. The description adds that it creates a scaffold with listed components, which is some behavioral context, but it doesn't explain side effects, network modifications, or what 'handoff scaffold' means operationally. With annotations covering the core mutation trait, 3 is appropriate.

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 description is a single, efficient sentence that front-loads the main purpose. It lists four components in a compact list, which is readable but somewhat packed. No wasted words, but slightly dense for easy parsing.

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 10-parameter tool with no output schema and only 20% parameter documentation, this description is under-specified. It tells the agent what scaffold to create but not how the bridge operates, what the parameters control, or how it integrates with the existing network. The description lacks the depth needed for correct invocation.

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 only 20% (2 of 10 params). The description mentions concepts like HDA, cache, parameter maps, and cook-status, which loosely relate to parameters but does not map or explain any specific parameters. It fails to compensate for the low schema coverage, so it falls below baseline.

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 uses a specific verb ('Create') and identifies a clear resource ('Houdini Engine/HDA/cache handoff scaffold') with concrete components (manifests, parameter maps, cook-status ingest, geometry cache notes). This clearly distinguishes it from sibling tools like create_engine_comp or connect_unreal_livelink_bridge.

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?

The description implies use when a Houdini Engine/HDA/cache handoff is needed, but it does not explicitly state when to use this vs alternatives, nor any exclusions or prerequisites. It relies on the purpose to imply usage, so it earns a baseline 3.

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