create_query

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

No annotations are provided, so the description must disclose behavioral traits. It only mentions saving and returning an ID, but does not specify side effects (e.g., overwriting, validation), error states, or rate limits. 'Requires Paid Plan' is helpful but insufficient.

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 two sentences, front-loading the purpose and return value. Every sentence earns its place with no redundancy.

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?

The tool has low complexity (3 simple params, output schema exists). The description covers the core action and a prerequisite, but lacks details on parameter constraints or typical usage patterns. It is minimally adequate but not fully informative.

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% and the description adds no meaning beyond parameter names. 'name', 'sql', and 'description' are self-explanatory, but the description does not clarify constraints (e.g., uniqueness of name) or format requirements.

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 action ('Save a new query to Dune'), the return value ('Returns Query ID'), and a prerequisite ('Requires Paid Plan'). It distinguishes from siblings like 'update_query' and 'execute_query' by focusing on creation.

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 mentions a prerequisite (Paid Plan) but lacks explicit guidance on when to use this tool versus alternatives like 'update_query' or 'execute_query'. The context is clear enough for an agent familiar with CRUD operations.

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