list_enemies

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so safety is covered. The description adds real behavioral context—that supplying level or steel_path changes the returned stats to that scaling—but it doesn't clarify whether the two stack or which takes precedence, and it says nothing about the result shape.

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?

Two tight sentences, front-loaded with the core capability and followed by the level/steel_path note. No filler, though the second sentence is slightly ambiguous in its use of 'or'.

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 5-parameter read-only tool with no output schema, the definition covers the main query path but leaves the limit parameter, default behavior, and result ordering undescribed. It is adequate to start a call but not fully complete.

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 only 40%, so the description must compensate: it usefully explains that level and steel_path yield scaled armor/health/shields and that faction filters the search. However, 'limit' is undocumented in both places, and 'level'/'steel_path' interaction ('or') is ambiguous given steel_path simply adds 100 levels, which suggests stacking rather than exclusion.

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 specific verb and resource ('Find enemies') and names the filterable dimensions (name, faction) plus the stats returned (armor, health, base level). It is clearly distinguishable from siblings like list_warframes or list_weapons, which cover different resources, though it doesn't explicitly call those out.

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 how to use the tool ('by name or faction') and hints that level or steel_path should be passed to get scaled stats, but it gives no explicit when-to-use vs when-not guidance and no mention of the limit parameter or defaults.

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