browser_storage_get_service_workers

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

No annotations are provided, so the description bears full burden for behavioral disclosure. It only states the action without mentioning side effects, required permissions, rate limits, or what 'state' entails. The minimal description leaves agents unaware of potential constraints or return behavior.

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 sentence, which is concise. However, it could provide more structure or detail without being lengthy. It sacrifices completeness for brevity, making it adequate but not exemplary.

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?

With no output schema and no annotations, the description should explain what the tool returns or provides. It mentions 'state' but does not define it, and references browser_docs for more info. This reliance on external documentation makes the description incomplete for autonomous agent use.

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 input schema has zero parameters, and schema description coverage is 100% (vacuously). The description adds no parameter information but also doesn't need to. The baseline for 0 params is 4, and the description meets that by clarifying the purpose without contradicting the schema.

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 retrieves service worker registrations and their state. It uses specific verbs 'Get service worker registrations' and references a resource. It distinguishes from sibling 'browser_storage_unregister_service_worker' which is for removal, making the purpose unmistakable.

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 for reading service worker state, and the sibling list provides context (e.g., unregister tool for removal). However, it lacks explicit guidance on when to use this tool versus alternatives like browser_docs or other storage tools, and no exclusions are stated.

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