mdx_explain

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states the tool explains the query but omits details about side effects, permissions, rate limits, or whether the explanation is static or AI-generated. This leaves the agent uncertain about behavioral traits.

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, front-loaded sentence that conveys the core purpose efficiently. It could be slightly more structured (e.g., listing what the explanation includes), but it remains concise without extraneous words.

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 the tool has one parameter and an output schema (which documents return values), the description addresses the primary purpose. However, missing usage guidelines and behavioral transparency leave gaps. For a simple tool, it is adequate but not fully complete.

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 0% for the single 'mdx' parameter. The description identifies it as an MDX query but does not specify format, constraints, or examples. The parameter's semantics are implied rather than explicitly defined, which is insufficient for an agent to construct valid input.

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 verb 'explain', the resource 'MDX query', and the output 'plain language covering measures, slices, and returns'. It effectively differentiates from sibling tools like mdx_run and mdx_ask by focusing on explanation rather than execution or questioning.

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 the tool is used for explaining MDX queries, but does not explicitly state when not to use it or mention alternatives. Given sibling tools, additional guidance on when to choose mdx_explain over mdx_ask or mdx_introspect would be helpful.

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