execute_query

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 behavioral traits. 'Execute an Analytical Query' and 'multi-dimensional analysis' imply a read-oriented computation, but the description does not mention whether any state changes occur, how results are returned, pagination behavior, or potential performance/rate-limit concerns. For a query tool this is a notable gap.

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?

Two sentences with no filler. The core purpose is front-loaded, and the discover_entities dependency is stated in the second sentence. Every word earns its place.

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?

This is a complex tool with 15 parameters, no output schema, and no annotations. The description covers the prerequisite workflow (discover_entities) but omits any guidance on the return format, required parameter combinations, or the analytical intent behind the many Cube flags. An agent would need to rely heavily on the schema alone, which is not enough for such a configurable 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 description coverage is 100%, so the schema already documents all 15 parameters, establishing a baseline of 3. The description adds a meaningful connection between entity_name and the discover_entities workflow, but it does not meaningfully clarify the many Cube-specific options (filters, timeDimensions, renewQuery, etc.) beyond what the schema already provides.

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 specific verb ('Execute') and resource ('Analytical Query'), and further clarifies with 'Perform multi-dimensional analysis on one of the entities discovered via discover_entities.' This clearly distinguishes it from the only sibling, discover_entities, which focuses on discovery rather than querying.

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 explicitly frames the tool as operating on entities discovered via 'discover_entities', establishing a clear prerequisite and workflow. It tells the agent when this tool is appropriate, though it does not enumerate explicit alternatives or negative cases. Since the sibling set is minimal, this is sufficient guidance.

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