superset_sqllab_format_sql

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

The description states the core behavior (pretty print with indentation) but does not disclose side effects or safety. Since no annotations are present, the description carries the full burden. However, the action is clearly a pure transformation, so a basic level of transparency is met.

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, front-loaded with the purpose, and an args list. No wasted 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?

For a simple one-parameter formatter with an output schema, the description is mostly complete. It could mention that the query is not executed, but that's inferable from the name and sibling context. Minor gaps in usage guidance exist.

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 schema has one required parameter 'sql' with no description. The description adds 'SQL query to format,' which clarifies the expected input, though it largely mirrors the parameter name. It does not specify constraints like valid SQL syntax or length limits.

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 formats a SQL query with pretty print indentation. This specific verb+resource combination distinguishes it from siblings like superset_sqllab_execute, making the purpose unambiguous.

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 offers no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, whether the SQL is executed, or any exclusions. An agent is left to infer that it's a formatting utility.

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