Delete Jedox Cube

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

The description reveals that deletion is irreversible and all cell data is lost, which goes beyond the annotations (destructiveHint: true). It also explains the need for an explicit save step to persist the deletion, adding significant behavioral context that annotations do not cover.

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 one-line purpose, a warning, a parameter list, a return type, and a post-requisite. Every sentence serves a purpose, and the critical warning is front-loaded. No unnecessary words or repetition.

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 deletion tool, the description covers the core action, data loss, parameters, and post-step. It does not address error conditions (e.g., cube not found) or side effects on dependent objects (openWorldHint: true). However, for the common use case, the information is sufficient.

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 input schema provides only type string with no descriptions (0% coverage). The description compensates by clearly explaining each parameter as 'Numeric ID of the database' and 'Numeric ID of the cube to delete'. This adds essential meaning beyond the schema, though it could include hints on how to obtain these IDs.

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 action ('Delete a cube and all its data') and the resource (a cube in a Jedox database). The warning about irreversibility reinforces the destructive nature. This uniquely identifies the tool among siblings that delete other entities like databases or dimensions.

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 does not explicitly compare to alternative delete tools, but the tool name and context make the use case obvious (deleting a cube). It provides a critical post-requisite: calling jedox_save_database to persist the change. This is a clear guideline for correct usage.

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