app_reload

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

Without annotations, the description provides key behavioral info: reloads web layer only, preserves Rust backend state. However, it does not disclose if the action is destructive, reversible, or requires any permissions, leaving some gaps for a mutation-tool-like action.

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?

Two sentences, no wasted words. First sentence states purpose, second clarifies scope (web layer only). Efficiently structured for quick comprehension.

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 no parameters and no output schema, the description is sufficient for the tool's simplicity. It covers purpose, scope, and effect. However, it could mention typical use cases (e.g., after UI errors) for extra completeness.

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?

With zero parameters, the schema provides no param details. The description adds value by explaining the tool's effect beyond the schema, thus meeting the baseline of 4 for zero-param tools.

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 reloads the webview to reset front-end state, distinguishing it from backend state persistence. It uses specific verb 'reloads' and resource 'webview', and differentiates from sibling tools like app_launch or app_close by focusing on state reset.

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 usage when a clean front-end state is needed but does not explicitly state when to use vs. alternatives. It mentions 'reset front-end state for a clean run' but lacks exclusions or references to sibling tools, leaving it to the agent to infer context.

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