neuron_reload

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Reload a tab' discloses only the literal action, omitting side effects (losing unsaved page state), wait/finish semantics, behavior on an invalid tabId, and return value. The action implies mutation of page state, but the description gives no context about its consequences.

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 three words with zero filler and the action verb is front-loaded. For a single-parameter tool, this is appropriately sized, though it borders on under-specification in other dimensions. It earns its place but doesn't go beyond it.

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 tool's low complexity (one fully documented parameter, no output schema, no nested objects) lowers the bar for completeness. However, with no annotations and no output schema, the description should at least note what happens after the reload (e.g., whether it waits for load, preserves the URL, or errors on a bad tab ID). Adequate for a trivial tool but with a clear gap.

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 description coverage is 100%, and the only parameter (tabId) is already documented as 'Chrome tab ID'. The description's 'Reload a tab' adds no new meaning to the parameter beyond what the schema provides. A baseline of 3 is appropriate since the schema does the heavy lifting.

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 'Reload a tab' states a specific verb and resource, making the core action unambiguous. It is semantically distinct from siblings like neuron_navigate, neuron_open_tab, and neuron_list_tabs, though it never explicitly names what it is not. A 5 would require explicit differentiation, but the meaning is clear enough for an agent to select it correctly.

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 provides no guidance on when to use this tool versus alternatives such as neuron_navigate (if the page is stuck) or neuron_open_tab (if the tab doesn't exist). There is no mention of preconditions, like the tab needing to exist, or exclusions. This is a total absence of usage direction, but not misleading, so it doesn't warrant a 1.

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