scaffold_kotlin_offline_resilience

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

With no annotations, the description carries the behavioral disclosure burden. It explains the core behavior: generating an interceptor that catches failures and serves cached/mock data without crashing. It does not mention side effects on the project, dependencies required, or what happens when the parameter is disabled.

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 sentence that front-loads the artifact and its purpose. The 'zero crash during live stage demos' phrasing is slightly promotional, but it does not bloat the description meaningfully.

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 scaffolding tool with one optional boolean parameter, the core purpose is clear, but the parameter is undocumented and there is no guidance on side effects, prerequisites, or behavior when the fallback is disabled. An agent cannot fully predict the impact of invoking this 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 0%, and the description does not mention enableDemoMockFallback at all. The parameter name and default value provide some semantic hint, but the description adds no meaning about how the boolean controls the fallback behavior, so it fails to compensate for the low schema coverage.

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 ('Scaffolds') and names a concrete artifact: an OkHttp fallback interceptor that serves cached/embedded mock data on network failure. This makes it clearly distinguishable from sibling tools like scaffold_kotlin_backend or generate_kotlin_mock_factory.

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 a use case: WiFi drops, network failures, and live stage demos. However, it gives no explicit guidance on when to choose this tool over other scaffolding tools or when not to use it, and no alternatives are mentioned.

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