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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses almost nothing: no auth requirements (the token param is unexplained), no pagination limits or total-count behavior, no return shape, and no rate-limit or error semantics. The GET verb implies a read-only operation, which is the only behavioral signal present.

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 short and front-loaded, but the raw URL is low-value for an agent that already has the tool name, and the terseness comes at the cost of missing context rather than being genuinely efficient.

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 and no output schema, the description must explain auth, pagination, and what distinguishes a compliance case from other case types, and it does none of these. Two parameters are present and only one is even mentioned.

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 both 'page' and 'token' are already documented in the schema. The description only echoes 'Optional page' and adds nothing about token acquisition, page-size behavior, or ordering, so the baseline of 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 states a clear verb+resource ('list compliance cases') and even names the underlying endpoint, so the agent knows exactly what it retrieves. It does not, however, distinguish this from the closely named siblings listCases and listDIYCases, leaving the 'compliance' scope ambiguous.

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 listCases, listDIYCases, or getCaseById, and no prerequisites or exclusions. 'Optional page' restates the schema rather than offering usage context.

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