invariance_case_list

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

Annotations already provide readOnlyHint; the description adds useful context: 'paginated' and visibility scope restricted to the calling agent. It does not contradict the annotations and makes no misleading claims about side effects.

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 tight sentences: the first front-loads the main action and pagination, the second lists available filters. No redundant wording or filler.

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 read-only, paginated list tool, the description plus schema adequately covers filter semantics and cursor handling. The lack of an output schema leaves return shape unstated, but this is a minor gap given the simple list operation and existing annotations.

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 only 25%, so the description compensates by enumerating six filter parameters and the status enum. However, it does not explain limit/cursor beyond what the schema already says and gives no additional format detail for outcome or tags.

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'), a clear resource ('cases'), and a scope ('visible to the calling agent'), plus pagination. This clearly differentiates it from siblings like invariance_case_get (single case) and invariance_case_create (write operation).

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 says what the tool does but gives no guidance on when to choose it over related tools such as invariance_case_get or invariance_finding_list. No alternatives or exclusions are mentioned, so an agent must infer usage context from the name alone.

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