memory_find_c2_connections

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

With no annotations provided, the description carries the full burden of disclosing behavior. It only states that it 'Finds suspicious network connections' and mentions implementation details, but does not reveal read-only status, output format, side effects, or any limitations. This is insufficient for a memory analysis 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 concise at two sentences, with the main purpose front-loaded. However, the second sentence about implementation details is somewhat extraneous and could have been used for more useful operational context, but it does not significantly hurt the clarity.

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?

Given no output schema, no annotations, and only 33% schema coverage, the description should provide much more context. It lacks information about return values, parameter semantics, when to use, and what the agent should expect. The description is minimal and does not compensate for these gaps.

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?

Only the required image_path parameter has a schema description. The booleans include_listening and include_legitimate are undocumented in both the schema and the description. The description does not clarify what these booleans control, leaving the agent to guess their semantics.

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 verb 'Find' and the resource 'suspicious network connections', which distinguishes this tool from siblings like memory_find_injected_code or memory_hunt_process_anomalies. However, it does not explicitly mention that it operates on a memory dump (though implied by the parameter) or scope the meaning of 'suspicious'.

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 given on when to use this tool versus alternatives. It does not mention preconditions, exclusions, or that other memory tools might have overlapping functionality. The implementation detail (Rust/Python) does not help the agent decide when to invoke it.

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