list_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 of behavioral disclosure. 'Current' weakly implies a live snapshot read, but nothing is said about whether this is read-only, what a session record contains, whether results are paginated/truncated by the count default, or what permissions are required.

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?

One short sentence with no filler, and the resource is front-loaded. It is efficient, though the extreme brevity sits near the line between concise and under-specified for a tool with seven parameters.

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?

Seven all-optional parameters, no annotations, and no output schema, yet the description explains nothing about return contents, result limits, or the distinction between this and list_admin_sessions. For a tool of this surface area the description leaves substantial 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?

Schema description coverage is 100%, so every filter parameter (vdom, count, dstaddr, dstport, srcaddr, policyid, resolve_vms) is already documented in the schema. The description adds no filter syntax, combination semantics, or defaults beyond what the schema states, so the baseline 3 applies.

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?

Names the resource (firewall sessions) and implies a list verb, which is the minimum viable. However it is a bare noun phrase with no verb, and it does not distinguish itself from the nearby sibling list_admin_sessions, which an agent could easily confuse for the same thing.

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 statement of when to use this tool, when not to, or which alternatives exist (e.g. list_admin_sessions, get_top_traffic, get_logs). 'Optionally filtered' hints that filters exist but gives no guidance on choosing between the unfiltered and filtered modes.

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