DataKiosk_createQuery

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

With no annotations, the description carries the full burden. It usefully discloses that execution happens remotely in the Kuudo deployment, but it does not describe side effects, permissions, asynchronous behavior, or what a successful creation returns. 'Catalog entry' adds confusion rather than behavioral clarity.

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 short and contains the essential 'Creates...' clause, but 'Catalog entry' is filler and the main action is not front-loaded. It could be reordered to lead with the behavior.

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?

For a mutation tool with no annotations and no output schema, the description is incomplete: it does not state what happens after a query request is created, what the response contains, or what inputs are expected. Although the schema is empty, enough ambiguity remains that an agent cannot confidently invoke 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?

The schema declares zero parameters, so the baseline is 4. The description adds no parameter-specific meaning, but there are no documented parameters to explain; the empty schema plus additionalProperties:true leaves room for runtime request fields, which the description does not address.

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 states a specific action and resource: 'Creates a Data Kiosk query request,' which distinguishes it from sibling get/cancel operations. The opening 'Catalog entry' is ambiguous, but the final clause gives a clear purpose.

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 does not say when to choose this tool over DataKiosk_getQuery, getQueries, or cancelQuery, and it offers no prerequisites or exclusions. 'Runs in your Kuudo deployment, not here' hints at environment context but does not guide selection.

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