pwa_add_offline

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only lists features (background sync, IndexedDB, fallback pages) without explaining side effects, whether files are modified or generated, required authentication, or how the 'Pro' qualifier affects behavior. This is a significant gap for a mutation-style tool.

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 compact, front-loaded sentence with no unnecessary elaboration. The only mild issue is the unexplained '(Pro)' suffix, which adds ambiguity without clear value.

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 tool with no output schema, no annotations, and four parameters, the description only supplies a feature list. It does not cover prerequisites, the relationship to other PWA generation tools, expected outcomes, or authentication requirements, leaving an agent without enough context to invoke it reliably.

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 the parameters are already documented in the schema. The description adds context by mapping high-level features to likely parameters (sync_endpoints, indexed_db_stores, offline_page), but it does not add meaning beyond what the schema already provides.

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 specifies the verb 'Add' and names the concrete resource: offline support, with the specific components background sync, IndexedDB storage, and fallback pages. It clearly communicates what the tool does and is distinct enough from sibling tools like pwa_generate_manifest and pwa_generate_sw, though it does not explicitly compare itself to them.

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?

No guidance is provided about when to use this tool versus alternatives such as pwa_generate_sw or pwa_generate_manifest. The description implies the use case through the name, but it does not state prerequisites, exclusions, or how to choose among the related PWA tools.

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