reload_plugins

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

With no annotations, the description carries the full behavioral burden. It does disclose the read source (plugins/*/plugin.json) and one side effect (macro registry refresh), but says nothing about whether the reload interrupts in-flight executions, whether a restart is required, whether it can fail on a malformed manifest, or what it returns.

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?

A single tight sentence with the action and its effect front-loaded and no filler. Nothing could be removed without losing information.

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-argument, no-output-schema tool this is minimally adequate: the agent knows what is reloaded and what is refreshed. It is missing the operational context that matters most for a state-refreshing tool — safety during active executions and expected outcome — which no annotation or output schema supplies.

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?

Zero parameters, so the baseline is 4; the schema is trivially complete. The description adds only the path glob, which is context rather than parameter semantics, so it neither gains nor loses here.

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?

Specific verb ('reload') plus resource ('plugins') and the exact source of truth ('plugins/*/plugin.json'), with the secondary effect ('refresh macro registry') stated. It is distinguishable from list_plugins and list_macros, though it does not explicitly contrast with reload_comfyui, the closest sibling.

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 never says when to invoke this tool — e.g. after editing a plugin manifest or installing a plugin — nor when not to. It also fails to distinguish it from reload_comfyui or to point at list_plugins as the inspection alternative, leaving the agent to infer the trigger condition.

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