Delete Jedox Dimension

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

Description adds beyond annotations: confirms destructive action, warns of failure if cubes exist, and suggests calling jedox_save_database afterwards. No contradictions.

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?

Compact and well-organized: purpose, warning, args, return, and follow-up action in a few lines. No fluff.

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?

Covers all essential aspects: action, precondition, required parameters, return value ('{ success: true }'), and necessary follow-up (save). Output schema absent but return described.

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?

Input schema already describes both parameters fully ('Numeric ID...'). Description merely restates them without adding new constraints or formats. Schema coverage is 100%, baseline of 3.

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?

Clear verb ('delete') and resource ('dimension'). Warning about cube dependency adds clarity. Distinct from other delete tools by naming and purpose.

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?

Provides a crucial prerequisite: cubes using the dimension must be deleted first. Does not explicitly state when to use vs alternatives, but the condition is clear enough.

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