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

The description provides substantial behavioral detail beyond the readOnlyHint annotation: it explains the version axis including release staleness, lanes, lag, exactness, and advisories. It also clarifies null vs. zero-count semantics ('all-zero counts mean tracked and clean, which is a different statement'), which is exactly the kind of nuance an agent needs to interpret results correctly. This goes beyond the annotation's simple read-only hint.

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 detailed but somewhat dense and runs on, particularly the parenthetical about lanes and the long sentence about exactness. It front-loads the core purpose well but then dives into complex details that could be more concisely structured. The length is justified by the complexity of the return data, but it could be better organized for readability.

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?

Given the complexity of the response (multiple roles, version staleness, advisories, null semantics) and the absence of an output schema, the description is quite complete in covering the key aspects an agent needs to understand the return data. However, it doesn't mention the output format (e.g., JSON structure) or how to interpret 'market tier' (which appears at the end without explanation). Overall, it's strong but with minor gaps.

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 input schema already describes both parameters (hostname and at) with reasonable clarity, and schema coverage is 100%, so the baseline for this dimension is 3. The description adds value by explaining the effect of `at` (point-in-time state) and repurposing it in the context of release staleness, though it doesn't add new syntax or format details beyond the schema. The extra clarity about `at` justifies a 4.

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 tool's purpose: 'Get a host's software fingerprint' and elaborates that it returns detected software across all roles, including vendor, version, hosting, confidence, timestamps, and evidence. This is specific and distinguishes it from siblings like get_software (which likely returns software-level data) and list_host_software (which lists multiple hosts' software).

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 that this tool focuses on a single host's software with optional point-in-time state (`?at=`), but it does not explicitly state when to use this tool versus alternatives like get_host, get_software, or list_host_software. There is no mention of when not to use it or how it differs from similar tools, which is a gap for an agent choosing among many siblings.

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