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

readOnlyHint=true already establishes the safety profile, so the description's job is additive context. It adds the scope of returned data and the underlying REST endpoint, but says nothing about permissions, whether hardware may be stale/missing for offline devices, or response 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 short sentences, zero filler, with the substantive description of what is returned front-loaded before the API reference.

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 single-parameter read tool with no output schema, the description adequately conveys both the input identity and the nature of the result. A note on behavior for devices with unavailable hardware data would push it higher.

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 100% and the single parameter is already documented as an agent asset GUID. The description adds only the placement of that id in the API path (/v1/assets/agents/{agentAssetId}/hardware), which is marginal value.

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?

Uses a specific verb plus resource and enumerates the returned data (processors, memory, disks), which distinguishes it from gorelo_get_agent_asset or the list endpoints. It does not explicitly name a sibling to use instead, so it stops short of a 5.

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?

Implicit guidance only: an agent can infer this is the tool for hardware detail on a known device. There is no statement of when to prefer it over gorelo_get_agent_asset or the list tools, and no prerequisites (e.g., needing the asset id from a list call) are stated.

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