get_network_context

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

No annotations are provided, so the description carries full burden. It only states what data is captured, not whether the operation is read-only, what happens with invalid target IDs, or if any side effects occur. The lack of any behavioral disclosure leaves significant ambiguity for an agent.

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 concise sentence that front-loads the core concept of network context. It avoids unnecessary verbosity and is appropriately brief for a simple get-type tool. However, it could be slightly more structured to separate the data from the action.

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 annotations, no output schema, and a single parameter, the description should clarify the return format and any prerequisites. It does not mention what the response contains beyond the captured context, nor does it state that a valid target_id is required. This is insufficient for an agent to confidently invoke the tool without further guesses.

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 0% and the description does not mention the target_id parameter at all. The description adds no meaning beyond the schema's minimal definition of an integer ID. The agent must infer that target_id refers to the target whose network context is being fetched, which is not explicitly stated.

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 deals with network context captured during scans, specifying the external IP and resolved IPs. It is distinct from siblings which focus on queues, tags, scans, and targets. However, it does not explicitly state that the tool retrieves or returns this context, leaving the action implicit.

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 guidance on when to use this tool versus alternatives. The description does not mention any preconditions (e.g., target must exist or have scans) or scenarios where this tool is preferred over others. The sibling list provides context but no explicit routing.

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