mdx_run

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

With no annotations, the description must disclose behavioral traits. It does so by clarifying read-only constraint and that it returns a single cell value. However, it lacks details on error handling, performance, or what happens if the query returns multiple cells.

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 a single sentence, very concise with no superfluous words. It efficiently conveys key information, though it could be expanded with an example without losing conciseness.

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 no annotations, no output schema, and only one parameter with no description, the description is insufficient for full context. It omits important details like error messages, syntax specifics, or time limits, leaving significant gaps for an AI agent.

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 coverage is 0%, and the description does not elaborate on the 'mdx' parameter beyond 'a provided MDX query'. No format, constraints, or examples are given, leaving the agent without guidance on how to construct the query.

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?

Description clearly states the tool executes an MDX query, specifies its read-only nature (SELECT/WITH only), and mentions returning a cell value. However, it does not explicitly differentiate from sibling tools like mdx_ask.

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 implies usage for read-only queries by stating 'read-only; SELECT/WITH only', but does not provide when to use this tool over alternatives like mdx_ask or mdx_explain. No guidance on when not to use.

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