censys_get_host

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

The description implies a read-only retrieval operation and discloses output content, but it does not explicitly state side-effect-free behavior, authentication needs, rate limits, or error handling. Since no annotations are provided, the description carries the burden of clarifying these behavioral traits.

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 concise, front-loaded with the main purpose, and uses a short bullet-style usage section. There is no redundant or filler content.

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?

The output schema is present, both parameters are documented, and the description captures the key deliverable categories. The only minor gap is the absence of explicit guidance on choosing between this and the host-search sibling tool.

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?

Both parameters are fully described in the schema, and the description adds meaningful input constraints such as 'without scheme or CIDR masking'. It also clarifies that at_time is used for historical host state, going beyond the schema's basic type information.

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 identifies the action ('Retrieve') and resource ('comprehensive intelligence and protocol details for a single host'). This distinguishes it from sibling tools like censys_search_hosts, which implies searching over hosts rather than fetching one host by IP.

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?

It gives practical constraints, such as requiring a raw IPv4/IPv6 address without scheme or CIDR masking, and lists the types of data returned. However, it does not explicitly mention when to use this tool instead of censys_search_hosts.

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