web_inspect_pwa_cache

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

No annotations are provided, so the description carries the full behavioral burden, yet it does not state whether the tool is read-only, what network or filesystem access is required, or that it writes audit artifacts to outputDir. It also does not address the sensitivity of extracting unencrypted credentials beyond naming the capability.

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 long, comma-heavy sentence that lists many capabilities without structural breaks. It is compact and front-loads the manifest audit, but the run-on enumeration makes it harder to scan than a deliberately structured summary.

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 schema fully documents all seven parameters, which reduces the description's burden, and the description does enumerate the main inspection capabilities. However, with no annotations and no output schema, it still omits prerequisites, side effects, and how the generated artifacts should be interpreted, leaving meaningful context gaps for a multi-feature audit tool.

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%, so every parameter including target, outputDir, and the generate/inspect flags is already documented in the input schema. The description adds no parameter-specific meaning beyond the operation names that the schema also covers, so the baseline of 3 is appropriate.

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 specific verbs and resources — auditing Web App Manifests, reverse-engineering ServiceWorker caches, extracting IndexedDB schemas — so the tool's scope is clear. However, it bundles several capabilities into one sentence and never distinguishes itself from siblings such as web_optimize_offline_cache, web_reconstruct_schema, or web_analyze_app_state.

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?

There is no explicit guidance on when to use this tool, when not to use it, or which sibling to choose for adjacent tasks like offline caching optimization or schema reconstruction. The intended use case is only implied by the tool name and by the listed inspection targets.

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