malcolm_related_sessions

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

No annotations are provided, so the description carries the full burden. It only states that it searches two fields and returns related sessions, but does not disclose behavioral traits such as safety, side effects, performance implications, or behavior when UID is not found. This is minimal for a tool with no annotations.

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 and front-loaded with the core purpose. It uses a docstring format for structure, with each sentence adding value. However, it could be slightly more compact (e.g., 'Args' section is not strictly necessary for 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 the tool's simplicity (2 parameters, output schema exists), the description is largely complete. It explains search fields and parameters. It could mention potential edge cases (e.g., empty results), but overall it adequately covers what the tool does for an agent to use it correctly.

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%, but the description adds meaning beyond schema titles: it describes 'uid' as a Zeek connection UID with an example, and 'limit' as maximum related sessions with a default of 50. This adds type, example, and default behavior, significantly improving over the bare 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's purpose: 'Find all sessions related to a Zeek UID.' It specifies the search fields (zeek.uid and related.zeek.uid), distinguishing it from siblings like arkime_sessions or malcolm_search which have broader scope.

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 when you have a Zeek UID and want related sessions, but does not explicitly state when to use this tool versus alternatives (e.g., arkime_sessions) or when not to use it. No exclusions or prerequisites are mentioned.

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