verfi_list_sessions

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose that results are paginated and include session status and metadata, and "List" implies a read-only operation, but it says nothing about ordering, auth/tenant scoping mechanics, rate limits, or whether unclaimed sessions are truly returned despite the opening sentence.

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?

Two short sentences with the core operation front-loaded and no filler preamble. "With session status and metadata" is slightly vague and borders on generic, but it is the only part that could be trimmed.

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 read-only list with three optional parameters, full schema coverage, and no output schema, the description covers the essentials: what is listed, the tenant scope, and that results are paginated with status/metadata. What remains missing is return ordering and the search-vs-list distinction, both of which an agent would likely want.

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% — page, limit ranges, and the claimed/unclaimed enum are all documented in the schema itself. The description only echoes the existence of pagination and adds no syntax, defaults, or filtering semantics beyond what the schema already states, so 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?

The description gives a clear verb and resource ("List sessions") plus an organizational scope ("claimed by your organization"), so the operation itself is unambiguous. It does not differentiate from the sibling verfi_search_session, leaving an agent to guess why two session-listing tools exist. There is also mild internal tension: it says sessions are "claimed by your organization" while the status enum explicitly offers "unclaimed".

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 when-to-use guidance is provided, and none of the eight siblings (notably verfi_search_session) are referenced as alternatives. The scope phrase hints at a tenant-wide listing, but nothing tells an agent when to pick this over searching or when to combine it with verfi_get_claim_status. Usage must be fully inferred.

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