create_query

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

With no annotations, the description must convey behavioral traits. It only states 'Create a new query' without disclosing side effects, required permissions, or system behavior (e.g., whether the query is saved immediately, if it triggers execution, or what happens on validation failure). The minimal description fails to inform the agent about the tool's operational characteristics.

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 extremely concise with a single sentence, containing no wasted words. However, it lacks structural elements like bullet points, examples, or breakdown of steps. The conciseness comes at the cost of informativeness, leaving it minimally adequate.

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 complexity (7 parameters, no output schema, no annotations) and the presence of many sibling tools, the description is insufficient. It does not explain the return value, prerequisites (e.g., valid data_source_id), or the difference between creating a query and other query operations. The description fails to provide a complete picture for an AI agent to use the tool effectively.

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 100% description coverage, providing basic meaning for all seven parameters. The description adds no additional value beyond what the schema already offers, so a baseline score of 3 is appropriate. There is no extra context about parameter relationships, constraints, or formatting.

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 verb 'create' and the resource 'query', making the basic purpose understandable. However, it does not distinguish the tool from sibling tools like 'create_query_snippet' or 'execute_query', which could cause confusion. A more specific definition of what constitutes a 'query' in Redash (e.g., a saved SQL query) would improve clarity.

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. Sibling tools include other query creation actions (create_query_snippet) and execution tools (execute_query), but the description does not help the agent decide between them. For a CRUD tool in a domain with many similar operations, this omission is significant.

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