thruk_run_background_query

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

No annotations are provided, so the description carries full burden. It mentions background=1 mechanism but does not explain how the result is retrieved (polling, job ID, etc.), whether it blocks, timeout behavior, or what happens on failure. The poll_timeout parameter suggests polling but is not described.

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 a single concise sentence. It is front-loaded with the core action and mechanism, but could be improved by adding structured details on usage and behavior without sacrificing conciseness.

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?

Given the tool has 6 parameters, async behavior (background=1), no output schema, and a potential poll_timeout, the description is too brief. It lacks information on how to use the tool effectively, what the response looks like, and how polling works.

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 33% (only path and backends have descriptions). The description adds no additional meaning to parameters; it does not explain data, method, params, or poll_timeout beyond default values. It fails to compensate for the low coverage.

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 tool runs long Thruk REST requests via background=1 mechanism. It identifies the purpose (execute long queries) and the mechanism (background=1), but does not explicitly differentiate from thruk_query or other query tools.

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 'potentially long' implying use for long-running requests, but provides no explicit guidance on when to use this tool versus alternatives like thruk_query, no prerequisites, and no exclusion criteria.

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