Create Jedox Cube Rule

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

Annotations are sparse (readOnlyHint=false, destructiveHint=false), but the description adds valuable behavioral context: rules take precedence over consolidation, need for single quotes, avoidance of circular references. This goes beyond what annotations provide, earning a 4.

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 front-loaded with a clear purpose, followed by examples and an args list. While slightly lengthy, each section adds necessary information without redundancy. Structured well for an AI agent.

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?

With no output schema, the description explicitly mentions the return format. It covers purpose, syntax, arguments, and behavioral notes. Lacks only explicit alternative tool guidance, but overall complete for a rule creation tool.

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 covers all parameters with descriptions (60% coverage), but the description adds syntax examples and JSON escaping guidance for the 'definition' parameter. This adds modest value beyond schema, justifying a 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?

The description starts with a clear verb and resource: 'Add a calculation rule to a Jedox cube.' This distinguishes it from sibling tools like create_cube or delete_rule, and the specific focus on rules is evident.

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 examples and warns about circular references and rule precedence, but it does not explicitly state when to use this tool versus alternatives like set_cell_value or bulk operations. The usage context is implied through syntax examples but lacks exclusions.

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