extension_dev_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. It states the mechanism ('through Chrome's extension-management UI') and the prerequisite ('installed unpacked'), but it does not disclose the runtime side effects of reloading, error behavior for invalid or missing ids, or whether the operation is asynchronous.

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, front-loaded sentence that states the action, object, qualifier, and mechanism with no filler. 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?

For a one-parameter tool, the description covers the core context: reload an installed unpacked extension by exact id via the extension-management UI. It is nearly complete, though a bit more detail about side effects or return behavior would make it fully self-sufficient given the absence of annotations and output schema.

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 schema provides only the pattern for 'id', so the description adds useful meaning by specifying it is the exact extension id. Still, with 0% schema description coverage, the description only lightly compensates and does not mention how to obtain the id or what happens with a non-matching extension.

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 uses a specific verb ('Reload') and a specific resource ('installed unpacked extension') with an exact-id qualifier. This clearly differentiates it from sibling tools like extension_dev_load, extension_uninstall, and extension_set_enabled.

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 implies when to use it: when an unpacked extension is already installed and needs reloading by exact id. However, it does not explicitly contrast this with loading, enabling, or removing extensions, so the agent must infer the decision boundary from sibling names.

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