reload_dry_run

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It discloses that the tool does not actually reload (safe, no side effects), which is critical. It does not detail output format or permissions, but for a simple preview tool, this is adequate.

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: just two sentences, no fluff. The first sentence states the core functionality, the second gives practical usage context. Every word earns its place.

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 (no parameters, output exists but described by schema), the description fully covers what an agent needs: purpose, usage context, and safety (no actual reload). No gaps.

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 zero parameters, so no parameter documentation is needed. Schema coverage is 100% and the description does not need to add parameter info. Baseline score 4 applies.

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 clearly states the tool's purpose: preview modules that would be reloaded without actually reloading. It uses a specific verb 'Preview' and resource 'modules', and distinguishes itself from sibling reload tools by emphasizing it is a dry run.

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 explains when to use it: 'when a user is about to press the reload everything button and wants to know the blast radius first.' This provides clear context, though it does not explicitly mention when not to use it or alternatives. Still, it is sufficient for the agent to determine appropriate use.

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