Reload bridge

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

The description discloses the key behavioral trait: hot-reloading Python modules in place and returning the list of reloaded modules. Annotations indicate mutation (readOnlyHint=false) but no destruction, and the description adds context about reimporting modules. It is clear but could elaborate on potential side effects like state resets.

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 extremely concise with two sentences: the first explains the action and benefit, the second adds operational detail and usage. Every sentence earns its place with no redundancy.

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?

Given the tool's simplicity (zero parameters, no output schema), the description adequately covers purpose, usage, and return value. It could specify the exact format of the returned list (e.g., list of module names), but overall it is sufficiently informative.

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 has zero parameters, so the description does not need to add parameter information. The baseline for zero parameters is 4, which is appropriate as there is no missing semantic value.

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 ('hot-reload') and resource ('bridge's Python inside running TouchDesigner'), clearly stating the tool's action. It distinguishes from siblings by focusing on bridge code reloading, which is unique among a list of creation/execution tools.

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 explicitly says 'Use after editing bridge code,' providing clear usage context. However, it does not discuss when to avoid using it or mention alternative approaches, which would strengthen guidance.

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