superset_saved_query_update

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states 'Update a saved query' without mentioning required permissions, side effects, error conditions, or whether the update is partial versus full replacement. The 'Pass only the fields to change' line is helpful but insufficient for a mutation tool.

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 two sentences plus a compact argument list. It front-loads the core purpose and immediately follows with the key behavioral instruction. Every line adds value, with no redundant text.

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's low complexity and the presence of an output schema, the description covers the essential inputs and the partial-update behavior. It omits edge cases like passing no updated fields or authorization requirements, but these are not critical for a straightforward update operation.

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 description adds meaning to all parameters by explicitly defining each one (e.g., 'label: New name', 'sql: New SQL query'). This goes beyond the raw schema types and clarifies that only saved_query_id is required, with the others being optional fields to change.

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 starts with 'Update a saved query', a specific verb+resource that clearly states the tool's purpose. It distinguishes from sibling tools like create, get, delete, and list by focusing on the update action.

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?

'Pass only the fields to change' provides clear guidance on how to use the tool for partial updates. It does not explicitly mention when not to use it or suggest alternatives, but the update context is unambiguous.

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