adl_targets

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

The readOnlyHint annotation already covers the safety profile, and the description adds a useful behavioral constraint that results come only from trusted local configuration. However, it does not explain whether the lookup is purely local, what happens when no targets are allowed, or any return 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 single sentence is front-loaded and free of redundancy, but its terseness leaves key terms like 'targets' and 'trusted local configuration' unexplained.

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 tool with one optional enum parameter and no output schema, the description should clarify what targets are, how 'surface' affects results, and how this differs from related adl_* listing tools. It does none of these, so an agent would need to infer too much.

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?

There is one optional parameter, 'surface' with enum values browser/desktop, but schema description coverage is 0% and the description never mentions the parameter. It therefore does not compensate for the schema gap or clarify what choosing a surface changes.

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 verb ('List') and resource ('targets') plus a filtering scope, but 'targets' is left undefined and it does not distinguish this tool from siblings like adl_applications or adl_capabilities.

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?

It implies the results are restricted to trusted local configuration, but gives no explicit guidance on when to use this tool versus adl_applications, adl_capabilities, or adl_app, and no exclusions or prerequisites are stated.

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