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

Annotations already declare readOnlyHint=true, but the description adds meaningful behavioral context: it lists the returned categories, explains the effect of `?at=`, and describes the conditional publishability and verification caveat of `profile`. It does not cover auth, rate limits, or pagination, but those are less critical for a read-only host lookup.

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 front-loaded with the core purpose and then provides relevant operational details in a compact paragraph. It is dense but not bloated, and every clause contributes useful context.

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 the main returned data and explains the `profile` field's conditional behavior. It remains incomplete regarding selection against sibling tools and does not describe pagination or error behavior, but it is sufficient to call the tool correctly.

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 the schema already documents both parameters. The description adds clarifying value for `at` (point-in-time state), but offers no additional detail for `hostname` and mentions `profile` as an output rather than a parameter. 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?

The description uses a clear verb+resource ('Get a host's current state') and enumerates the returned information (role, verdict, network attribution, TLS certificate, provider). It does not explicitly differentiate itself from siblings like get_host_software or get_host_uptime, so it falls 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?

The mention of current state and the `?at=` parameter implies when the tool is useful (current vs. point-in-time host state). However, there is no explicit guidance on when to choose this tool over sibling alternatives such as get_host_software or list_hosts.

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