editor_reload_plugin

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

With no annotations provided, the description fully carries the burden of behavioral disclosure. It thoroughly documents that the plugin is disabled/re-enabled on the next frame, that plugin-managed reloads kill the server and drop the WebSocket transport, and that externally launched reloads wait up to 15 seconds and raise PLUGIN_DISCONNECTED on timeout with recovery diagnostics.

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 well-structured with a brief purpose statement followed by bulleted details for each launch mode. Every sentence provides essential information about behavior, response shapes, and recovery steps, with no wasted words given the operational complexity.

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?

The description comprehensively covers the tool's behavior across both plugin-managed and externally launched contexts, including transport drops, session reconnection, timeout errors, and output shapes. Since an output schema exists, detailed return values are optional, but the description goes beyond that by explaining the conditional flows and recovery diagnostics.

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 input schema has 100% coverage for the single optional session_id parameter, including its description 'Optional Godot session to target. Empty = active session.' The tool description adds no additional parameter guidance, but per the baseline for high schema coverage, this is sufficient.

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 opening sentence 'Reload the Godot editor plugin' uses a specific verb and resource, clearly identifying the tool's function. The description further distinguishes it by detailing the reload process and its context-dependent outcomes, setting it apart from sibling tools like editor_manage or session_manage.

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 clearly explains when this tool is used (to reload the plugin) and provides explicit follow-up guidance: in plugin-managed mode, reconnect and call session_manage(op='list') to find the new session_id. It does not explicitly state when not to use it or alternative tools for other purposes, but the context is clear and actionable.

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