DataKiosk_cancelQuery

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

No annotations are provided, so the description must disclose behavioral details itself. It does mention that the tool runs in the user's Kuudo deployment rather than 'here,' and that cancellation happens, but it omits important behaviors like whether cancellation is irreversible, what happens to associated documents/results, permission requirements, or error/idempotency behavior.

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, but it opens with low-value filler ('Catalog entry') and a vague execution-context sentence before finally naming the action. The actual operation is not front-loaded, and at least one sentence does not earn its place.

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?

With no output schema and no annotations, the description should explain how to obtain queryId, what cancellation means for the query lifecycle, and what response or errors to expect. The description covers only the basic action and names the parameter, leaving too much for the agent to infer.

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 zero properties, so the description's mention of a 'queryId parameter' is essential and adds meaning the schema cannot convey. It correctly signals that a queryId is needed, though it does not specify the value's format, source, or whether it is strictly required.

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 clear verb ('Cancels') and a specific resource ('the query specified by the queryId parameter'), making the tool's purpose immediately understandable. It also distinguishes itself from sibling DataKiosk operations like createQuery, getQuery, and getQueries via the cancel action.

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?

There is no guidance about when to use this tool versus alternatives, such as when to cancel a query as opposed to retrieving it or leaving it running. The description only restates the action and provides no context about prerequisites or relationships to sibling tools.

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