omni_pdb_traffic_correlate

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

No annotations are provided, so the description must disclose behavioral traits, but it does not say whether the symbol resolver contacts a network symbol server, whether vault header inspection requires DPAPI/Keystore access, or whether any mode writes files or has side effects. The verbs imply operations but leave the agent without essential safety and execution context.

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 with no wasted filler, but it is a dense slash-separated noun phrase rather than a front-loaded action statement. It is compact yet hard to parse, and the three capabilities would be clearer as a structured list.

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?

This is a multi-mode forensic tool with no annotations and no output schema, so the description needs to explain mode-specific behavior, outputs, and limitations. Instead it only names the three capabilities, leaving the agent without enough context to invoke each mode confidently.

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 coverage is 100%, so the input schema already documents both parameters and the action enum. The description implicitly maps each of its three capabilities to the corresponding enum value, but adds no further syntax, constraints, or per-mode parameter meaning beyond what the schema 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 names three specific capabilities with concrete resources: PE/PDB GUID lookup, encrypted vault header inspection, and HAR-to-OpenAPI synthesis. It is clear what the tool does overall, but it does not differentiate this tool from relevant siblings such as omni_inspect_symbol, omni_bsim_vault, or omni_native_tls_tracer.

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 choose this tool over its many siblings, nor any prerequisites or exclusions. The action enum implies three modes, but the description does not explain the selection conditions for any of them.

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