nexus_create_case

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

Lacks any behavioral details such as side effects, required permissions, idempotency, or what constitutes a valid case. With no annotations, the description carries full burden but only states the basic action.

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?

Single sentence with no superfluous information, but brevity sacrifices necessary context for a create tool. Efficient, but arguably under-specified.

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?

Does not explain what a compliance case is, post-creation behavior, uniqueness constraints, or any related context. For a creation tool with no output schema, more details are 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%, and the description adds no new meaning beyond the schema. Baseline 3 is appropriate, as the description does not enhance understanding of parameters.

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?

Specifies the action (create) and resource (compliance case), clearly distinguishing from retrieval tools like nexus_get_case and nexus_list_cases. However, it does not explicitly differentiate from sibling creation tools (none present), so it's clear but not exceptional.

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 guidance on when to use this tool versus alternatives, no prerequisites, constraints, or recommended usage context provided.

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