peaka_create_query

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

Annotations indicate readOnlyHint=false and destructiveHint=false, meaning the description must clarify behavior. It states the tool creates a new query (write but not destructive) and returns an ID for future execution, adding lifecycle context beyond annotations. It does not detail side effects on existing resources, but the creation behavior is clear.

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 concise sentences plus a focused paragraph on projectId prerequisites. Every sentence adds value, no fluff, and important information is front-loaded.

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 description covers the main purpose, return value, and a critical prerequisite (projectId). For a 5-parameter creation tool with no output schema, it is mostly complete. The distinction between PLAIN and MATERIALIZED query types is left to the schema, which is acceptable. The description could have mentioned the schedule parameter's purpose, but the schema describes it.

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?

With 100% schema coverage, the baseline is 3. The description does not elaborate on parameter meanings beyond the schema, except for a usage hint about projectId. The schema already provides adequate descriptions for all parameters including the nested schedule.

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 the specific verb 'Create' with the resource 'named, saved query' and identifies the Peaka project's semantic layer. It also mentions the return value (query object with ID) and how it connects to peaka_execute_query, distinguishing it from siblings like peaka_get_query or peaka_execute_query.

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 explicitly advises calling peaka_list_projects first if the projectId is unknown, and to ask the user for confirmation—providing clear when-to-use guidance and a direct alternative tool reference.

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