browser_reload_extensions

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

No annotations are present, so the description carries the full burden. It discloses that the tool targets unpacked/development extensions, but it does not mention side effects, behavior when extensionName is omitted, whether it reloads all extensions, or any prerequisites. Significant behavioral unknowns remain.

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 a single concise sentence with no wasteful words, front-loading the action and the target. It is well-structured and easily parsed, though very brief.

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?

With one optional parameter, no annotations, and no output schema, the description leaves critical gaps: the parameter is unexplained, the scope of the reload is ambiguous, and side effects are undeclared. It is not sufficient for an agent to confidently invoke the tool without additional context.

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 a single parameter (extensionName) with no description, and the tool description does not mention it at all. With 0% schema description coverage, the parameter's meaning and usage are completely unexplained, leaving the agent without guidance on how to populate it.

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 action ('reload') and the resource ('unpacked/development browser extensions'), distinguishing it from sibling tools like browser_list_extensions or enable/disable. It is specific and unambiguous.

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 intended usage (during development to reload unpacked extensions) is implied but not explicitly stated. No alternatives or exclusions are provided, though the description does give some context by limiting to unpacked/development extensions.

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