execute_query_pivot

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

No annotations are provided, so the description must fully disclose behavioral traits. It does not mention whether the tool is read-only, if it requires specific permissions, what side effects exist (e.g., logging), or any rate limits. The description only says 'execute,' which implies a function call but lacks detail on output or mutability.

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 clearly convey the purpose and usage context without any filler. The description is front-loaded with the action and resource, then the use case. Every sentence 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?

The description covers the basic purpose but lacks details about outputs, errors, or prerequisites (e.g., database connection, MBQL syntax). Given no output schema and no annotations, the description is somewhat incomplete for an execution tool, but it does convey the primary intent.

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?

The input schema has 1 parameter (input) with a nested query object described as 'MBQL pivot query object' in the schema, but the tool description adds no additional meaning about how to structure or use the parameter. With schema description coverage at 0% (as per context), the description does not compensate for the lack of parameter guidance.

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 tool executes a pivot query against a Metabase database, specifying the action (execute), the resource (pivot query), and the use case (pivot table visualizations aggregating data across multiple dimensions). This distinguishes it from generic query execution tools like execute_query.

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 a clear use case: 'Use this for pivot table visualizations that aggregate data across multiple dimensions.' This tells the agent when to use it, but it does not explicitly mention when not to use it or compare it with similar sibling tools like execute_card_pivot or pivot_dashcard_query.

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