List HTB Machines

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description earns credit for adding real context beyond them: the 1h list cache and that noCache bypasses it. It also discloses the returned row shape, which matters because there is no output schema. It omits any auth/rate-limit or pagination-size details.

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?

Three tightly packed sentences: purpose and default first, parameter routing second, return shape and caching last. Every clause carries information and nothing is redundant.

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?

With no output schema, the description usefully enumerates returned fields (id, name, os, difficulty, points, active, spawned, free) and explains caching, making the tool callable without surprises. It does not say how many rows a page returns or the total page count, a minor remaining gap.

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 description coverage is 100%, so all four parameters (page, filter, spTier, noCache) are already documented in the schema. The description restates the filter/spTier behavior and the page-1 default without adding syntax or format detail beyond the schema, so baseline 3 is appropriate.

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?

States a specific verb and resource ('List Hack The Box machines') and immediately clarifies the default scope (playable list, page 1). It does not explicitly differentiate itself from the sibling htb_machine_search, so it falls short of a 5, but the purpose is unambiguous.

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?

Gives clear parameter-selection guidance: 'use filter for retired, todo, or unreleased lists, and spTier for Seasonal/starting-point tier lists.' This tells the agent which argument selects which list. It stops short of a 5 because it never states when to prefer this over htb_machine_search or htb_machine_active.

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