Create case

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It states the core action (creating a case) but does not mention potential side effects, validation requirements beyond the required subject, permission needs, or what response is returned. It adds only minimal input-shape context about 'customFields'.

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 front-loaded sentence with no wasted words; the core purpose appears first, followed by a clarifying parenthetical and a brief shape note. It is concise and readable. Its brevity is a strength, though it leaves semantic gaps.

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 create operation with 9 parameters, no output schema, and no annotations, this description is under-specified. It does not explain the required subject field, parameter semantics, customFields structure, or return behavior. An agent would need additional documentation or reasoning to invoke it confidently across varied inputs.

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 0%, so the description must compensate, but it only says the tool accepts 'base fields plus a nested customFields object.' It does not explain the meaning of subject, stageId, statusId, category, priority, contactName, description, or contactPhone. The lone structural hint about customFields is helpful but far from sufficient for a 9-parameter tool.

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 and resource: 'Create a case,' and clarifies the ambiguous term with '(support ticket / פנייה)'. This distinguishes it from create tools for other resources like contacts, leads, tasks, and quotes. It does not explicitly contrast with the sibling gambot_update_case, but the create/update distinction is inherent in the verb.

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 gives no guidance on when to use this tool versus alternatives such as gambot_update_case, gambot_get_case, or other create tools. There are no explicit conditions, prerequisites, or exclusions. The intended usage is only implied by the verb 'Create'.

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