qui_list_orphan_scan_runs

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

Annotations already declare readOnlyHint=true, and the description's mention of GET aligns with that. However, it adds no additional behavioral context such as pagination, response size, or potential side effects. It does not contradict annotations, so a baseline 3 is appropriate.

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 sentences, front-loaded with the endpoint, and every word serves a purpose. It is concise and well-structured with no redundancy.

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 very generic schema and no parameter details, the description is minimally sufficient for a simple read-only list operation, but lacks explicit statement of what is listed and any query parameter documentation. The output schema covers return values, so that is not a gap, but the missing parameter specifics make it incomplete.

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 schema description coverage at 0%, the description offers a general convention for passing path/query/body parameters, but does not enumerate specific parameters like instanceID or any query parameters. It adds some meaning beyond the free-form schema but is insufficient to fully specify the call signature.

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 identifies the specific GET endpoint /instances/{instanceID}/orphan-scan/runs, which clearly maps to listing orphan scan runs. It is specific in verb (GET) and resource, but does not explicitly distinguish it from sibling tools like qui_get_orphan_scan_run that retrieve a single run.

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 explains how to pass arguments (path variables directly, query values in arguments.params, body in arguments.body) but does not provide guidance on when to use this tool versus alternatives. No context, prerequisites, or exclusions are given.

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