reload_plugin

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

With no annotations, the description carries the burden of disclosing behavior. It usefully states what is reloaded (Houdini-side plugin code) and what is not (MCP server tool definitions), but it does not cover side effects, permissions, error behavior, or whether the operation is reversible.

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 definition is front-loaded with the core purpose and then adds essential caveats in two short sentences. Every sentence earns its place, and there is no redundant or filler content.

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 zero-parameter development tool with no annotations or output schema, the description is largely complete: it explains what the tool does, when to use it, and its key limitation. A small gap remains around return behavior and explicit sibling differentiation, but nothing critical is missing 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?

The tool takes no parameters, so per the rubric the baseline is 4. The description correctly does not discuss parameter semantics, and there is no schema detail that needs compensation.

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 specific verb and resource: re-importing the plugin's Houdini-side code without restarting Houdini. It is clear, but it does not explicitly differentiate itself from sibling tools such as reload_hda, leaving some room for confusion about which reload operation to choose.

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?

It gives a clear context for use: after editing the server's handlers during development, this tool picks up the edits in the running session. It also notes that MCP server tool definitions are not reloaded and that a client reconnect is needed for those, but it does not name alternative sibling tools for related reload operations.

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