Create Jedox Cube

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

The description adds critical behavioral details beyond annotations: the dimension order is permanent and affects cell value access, and the change requires a subsequent save call. Annotations only indicate mutability, but the description explains the persistence mechanism and ordering constraints.

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 concise (a few lines), well-structured with Args and Returns sections, and front-loaded with the purpose. Every sentence adds value.

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 three parameters, no output schema, and the need to explain persistence and ordering, the description is complete. It covers return format, required post-step, and cross-references to sibling tools.

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?

The description adds significant meaning for database_id (numeric ID) and dimension_ids (ordered, from list_dimensions, permanent order). For name, schema already had description. Overall, it compensates for schema coverage gaps and clarifies parameter semantics.

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 'Create a new cube in a Jedox database by specifying which dimensions it spans.' This is a specific verb+resource combination that distinguishes it from sibling tools like create_database or create_dimension.

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 provides a clear instruction to call jedox_save_database afterwards, and references related tools for cell operations. However, it does not explicitly state when to use this tool versus alternatives like jedox_create_dimension or prerequisites (e.g., dimensions must exist).

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