update_query

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 says 'Update an existing query' and does not mention whether unspecified fields are overwritten, whether changes are reversible, what permissions are required, or what the response contains. This is a significant transparency gap for a mutation tool with complex effects.

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 concise sentence that is front-loaded with the verb and resource. It is appropriately sized and avoids clutter, but it is so short that it provides minimal information, although that is more an issue for other dimensions than for conciseness itself.

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?

This is a complex tool with 10 parameters, no output schema, and no annotations. The description fails to explain return values, update behavior (e.g., partial vs full update), or any context for when to invoke it. It is completely inadequate for an AI agent to understand the tool's full impact.

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 100% coverage with each parameter described, so the baseline is 3. The description adds no extra meaning beyond the schema, but the schema itself provides sufficient documentation for parameter semantics.

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?

Description clearly states the action ('Update') and the resource ('an existing query in Redash'), which distinguishes it from sibling tools like create_query, archive_query, and get_query. The scope is 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?

No guidance is provided on when to use this tool versus alternatives like create_query or archive_query. There is no mention of prerequisites, required fields, or scenarios where this tool is preferred. The description is a bare action statement with no usage context.

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