web_inspect_crdt_state

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 reads as a feature list. It never states whether 'target' as a URL triggers live network access, what permissions are needed, whether WebSocket frames are captured live or read from disk, or what the generated artifacts contain beyond their filenames. The composite, potentially heavyweight nature of the tool is undisclosed.

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?

It is a single sentence with no filler words, but it is a dense, comma-chained list of four capabilities rather than a front-loaded statement of purpose. The agent must parse the whole run-on to extract what the tool does, and the visualizer clause adds length without routing information.

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 five parameters, no output schema, and no annotations, the description should explain behavior and outputs more fully. It covers the capability surface and the schema covers the flags, but how the target is consumed, what capture is required for WebSocket input, and what the audit artifacts report are left implicit.

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 all five parameters, including the three generate flags and outputDir, are already documented in the schema. The description adds no syntax or format meaning beyond that, so the baseline 3 applies.

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 named resources: 'decompiles... CRDT state synchronization protocols (Yjs, Automerge, Liveblocks, ShareDB),' 'decodes binary vector clocks,' 'reconstructs document state trees.' This is far more concrete than a tautology, but it stacks four distinct capabilities into one tool, making it hard to know the single primary action, and it never names a sibling it differs from.

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 when-to-use guidance, no prerequisites, and no exclusions. An agent cannot tell from the text when to pick this over web_decompile_bundles or web_analyze_app_state, which plausibly overlap with bundle and app-state inspection.

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