autoflow_reload_tab

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

No annotations are provided, so the description carries the burden of explaining behavior. It does so by disclosing that the action is a forced reload and that the extension bridge is re-mounted, which implies a non-graceful reset of the tab state. It could mention potential disruption to in-progress operations, but 'force-reload' already signals that.

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, tightly written sentence that front-loads the action and then provides the triggering condition. Every word earns its place, with no redundant phrasing or filler.

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 zero-parameter recovery action with no output schema, the description is complete: it states what the tool does, what it re-mounts, and when to invoke it. No additional context is needed for an agent to call it correctly.

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 tool has zero parameters and the schema is empty, so there are no parameter ambiguities to resolve. Per the baseline for zero-parameter tools, the description need not add parameter-level detail, and it appropriately focuses on the action and condition.

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 names a specific verb ('force-reload'), a specific resource ('the Google Flow project tab'), and a distinct secondary action ('re-mount the extension bridge'). This clearly separates it from siblings like autoflow_heal_flow or autoflow_status, which target different concerns.

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 a clear condition for use: 'if the web app appears frozen or unresponsive.' It does not explicitly name alternative tools or state when not to use it, but the triggering context is concrete enough for an agent to select it appropriately.

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