workiva_wdata_cancel_query_run

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It only states 'Cancel' without mentioning side effects (e.g., irreversibility, only running runs can be canceled), error conditions, or required permissions. This is insufficient for a mutation-like operation.

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: one clear sentence followed by a compact parameter list. No wasted words, and the purpose 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 tool is simple with two parameters and an output schema, so the basic elements are present. However, given the lack of annotations and the complexity of Wdata query runs, the description omits important context like typical usage scenarios, potential errors, and whether the operation is idempotent or requires a specific run state.

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 has no parameter descriptions (0% coverage), so the description must compensate. It adds 'query_id: The query UUID' and 'run_id: The run ID', which clarifies the roles slightly beyond the schema's titles, but does not explain how to obtain or validate these IDs.

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 'Cancel a Wdata query run' with a specific verb and resource. It distinguishes itself from siblings like wdata_run_query and wdata_get_query_result by being the only cancel operation for query runs.

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 provide any explicit guidance on when to use this tool versus alternatives, such as when the run is in a cancellable state or if there are any prerequisites. It only implies usage through the verb 'cancel', but lacks context or exclusions.

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