superset_saved_query_create

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

With no annotations, the description carries the full burden of behavioral disclosure but only lists parameters and the action 'Create'. It does not mention permissions, return behavior, uniqueness constraints, validation, or side effects beyond the creation itself, similar to the 'Update shared drive settings' middle example.

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 concise one-liner followed by a compact, well-formatted args list. Every element provides useful information with no redundant detail.

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?

Despite no annotations, the description fully covers all parameters and their purpose, which is sufficient for a simple create operation. It omits return values, but since an output schema exists, that is acceptable. It could add more context about prerequisites or error cases, but the current coverage is solid.

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%, yet the description provides human-readable explanations for all five parameters, including a source hint for db_id and an example for schema ('public'). This adds significant meaning beyond the raw schema types.

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 uses a specific verb ('Create') and resource ('saved SQL query') with its purpose ('for reuse'), clearly distinguishing it from saved_query_list/update/delete siblings.

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 saving reusable SQL queries, and the arg details note that db_id comes from superset_database_list, providing a cross-tool reference. However, it does not explicitly state when to use this over alternatives like superset_sqllab_execute or saved_query_update, so guidance remains implicit.

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