create_case

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

No annotations are provided, and the description adds minimal behavioral disclosure. It does not mention idempotency, permissions, side effects, or what happens upon creation (e.g., returns case ID). The output schema exists but is not referenced.

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 with the core action 'Create a case'. It efficiently uses two sentences to convey key constraints, though it could be slightly more structured.

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?

Lacking annotations and with incomplete parameter guidance, the description is insufficient for a tool with 5 parameters. It does not explain the required name parameter or cover the output, leaving an agent underinformed.

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?

With 0% schema description coverage, the description adds meaning for case_stage and status, clarifying that case_stage must match an existing stage and status is 'open' or 'closed'. However, it omits semantics for name, description, and practice_area, leaving gaps.

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 'Create a case' with a clear verb and resource. It distinguishes from sibling tools like create_case_stage or create_client by targeting the case entity, though it does not explicitly differentiate from other creation tools.

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. It provides constraints for case_stage and status values but lacks context on prerequisites or conditions for creating a case.

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