List Targets

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

With no annotations, the description carries the disclosure burden. It reveals the ordering behavior, but does not state whether the operation is read-only, whether it requires permissions, or whether results are paginated. The lack of a safety profile annotation is partly offset by the obvious read nature, but more context would help.

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 sentence containing both the action and the key ordering constraint. Every word earns its place, and the most important behavioral detail 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?

For a parameterless list operation with an output schema, the description is nearly complete. It does not explain when to choose this over list_target_packs, but the core function is sufficiently clear for an agent to invoke it correctly without further detail.

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 tool has zero parameters, and the schema coverage is trivially 100%. Per the rubric, a zero-parameter tool gets a baseline of 4; no parameter descriptions are needed or possible.

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 operation: listing target companies, and adds the ordering rule 'highest priority first.' It distinguishes itself from siblings like list_target_packs and add_target_company by specifying the exact resource (target companies).

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 intended use is implied: call this when you need to see all target companies. However, it does not explicitly state when not to use it or mention alternative tools like find_warm_paths or list_target_packs, leaving some ambiguity for an agent navigating many siblings.

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