list_targets

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

With no annotations, the description carries the transparency burden. It explains the content coverage (simulators, hardware, cloud) and that entries include selection snippets and doc URLs, but it does not describe the return format, potential side effects, or whether data is fetched remotely. This is an acceptable disclosure for a simple listing tool but not exhaustive.

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 well structured: a concise one-sentence summary, an explanatory paragraph with the supported categories and guidance, a clear usage trigger, and a compact Args section. Every sentence adds value and the most important information appears first.

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 low-complexity tool with one optional parameter and no output schema, the description covers purpose, when to use it, what categories are included, and the parameter semantics. It is sufficient for an agent to select and invoke the tool correctly without additional context.

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 coverage is 0%, so the description fully compensates by documenting the 'category' parameter with its allowed values: 'simulator', 'hardware', or 'cloud'. This adds meaningful semantics beyond the bare schema, which only shows a nullable string with a default of null.

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 verb ('List') and the resource ('CUDA-Q execution targets (backends)') and adds that it provides guidance on choosing. It distinguishes itself from sibling documentation/search tools by focusing on available execution backends.

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 gives explicit usage guidance: 'Call this when deciding where to run a kernel or when the user names a provider.' It does not mention when not to use it or name alternatives, but the context is clear enough for the common cases.

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