dbgprobe.plugin.reload

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

Discloses the effect (re-imports module and refreshes tools) and requirement, but omits potential side effects like disruption to debug session or state preservation. No annotations to compensate.

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?

Description is two sentences, front-loaded with action, and contains no wasteful words.

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 single-parameter, straightforward action, the description covers purpose, effect, and prerequisite. Lack of output schema is fine; could specify success confirmation but not essential.

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 coverage is 100%, and the description adds no extra meaning beyond the schema's parameter description. The parameter is straightforward.

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?

Description clearly states the action ('Hot-reload') and the resource ('plugin by name'). It distinguishes from sibling tools like dbgprobe.plugin.load by specifying 'reload' and 'refreshes 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?

Description mentions a prerequisite (DBGPROBE_MCP_PLUGINS env var) and implies use when a plugin is already loaded, but does not explicitly contrast with dbgprobe.plugin.load or provide when-not-to-use scenarios.

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