Read the host hardware ID (sUNC gethwid)

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

Annotations already cover readOnly/idempotent/non-destructive, but the description adds real value beyond them: it is type-guarded and pcall-wrapped, cites the exact error string returned when gethwid is unavailable, notes cost=medium, and states the active-client prerequisite. It does not, however, describe timeout or thread-identity behavior in any depth.

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?

Purpose and return shape are front-loaded, and the sentences are dense but information-bearing. Minor redundancy appears where 'idempotency=read-only', 'Safety: read-only', and the annotations repeat each other.

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 two-param read tool with no output schema, the description cnumbers the return contract ({ hwid } or { error }), the executor dependency, and the failure mode, which is sufficient. It lacks any cross-reference to related lookup tools, a small 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 both parameters (threadContext, timeoutMs) are already documented in the schema. The description merely reprints the signature with no added semantics or format guidance. Baseline 3 applies when the schema carries the load.

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 ('Read the host machine's hardware identifier (HWID) via the executor's gethwid()') and immediately explains its use case (stable per-machine fingerprint for key/license binding). No sibling tool reads HWID, so the agent can distinguish it easily.

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 implies the use case (license/key binding), but never explicitly says when to prefer this over alternatives such as get-executor-info or get-game-info, nor any when-not conditions. Prerequisites ('Requires gethwid', 'Requires: active-client') are stated, which is more than nothing but not routing guidance.

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