nexus_list_cases

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

With no annotations, the description must cover safety and behavior. It mentions authentication and filtering but omits requirements (e.g., permissions), whether it returns only user's cases, or rate limits. The behavioral disclosure is insufficient.

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 a single sentence that conveys key information without waste. It is appropriately sized and front-loaded with purpose.

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?

Given no output schema and no annotations, the description lacks context about return format, ordering, error handling, or pagination details. For a list operation, more completeness is needed.

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 100%, so baseline is 3. The description's 'Supports pagination and status filter' paraphrases schema descriptions without adding new meaning. No additional semantic value beyond schema.

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 clearly states the verb 'List', the resource 'compliance cases', and the user scope 'for the authenticated user'. It also mentions key features like pagination and status filter, distinguishing it from sibling tools like nexus_get_case.

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 implies usage for listing cases but does not explicitly state when to use this tool versus alternatives like nexus_get_case for single case retrieval or nexus_create_case for creation. No exclusion or alternative guidance is provided.

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