net_intercept_list

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

With no annotations, the description itself must carry behavioral disclosure. 'List active... rules' accurately conveys a read-only operation, but it does not explain what 'active' means, what happens when sessionId is omitted, or the output shape.

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?

A single front-loaded sentence with no filler. Every word adds semantic content.

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?

For a simple one-parameter list tool, the core operation is stated, but the absence of annotations and output schema leaves gaps around sessionId defaulting, return content, and relationship to sibling list/filter tools.

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%, so the description must compensate. It only says 'for a session,' which maps loosely to sessionId but does not clarify that the parameter is optional, what value to pass, or what occurs when it is omitted.

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?

States a specific verb ('List'), resource ('active network intercept rules'), and scope ('for a session'). The term 'intercept rules' clearly distinguishes this from network-list siblings like net_list and from mutation tools net_intercept_add/net_intercept_clear.

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?

Provides no guidance on when to use this tool rather than net_list, net_intercept_add, or net_intercept_clear. There are no exclusions, prerequisites, or context cues beyond the phrase 'for a session.'

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