Hostinfo Tool

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

readOnlyHint=true already declares the safety profile, so the description isn't obliged to repeat it. It confirms the read is a fixed identity lookup with no inputs, but omits anything about whether it describes the local or a remote host, any permission requirements, or caching/freshness.

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?

Short and front-loaded, with the resource named in the first clause. The trailing 'Returns: Hostname, kernel, and OS details' largely restates the first sentence, so one line is not earning its place.

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 zero-param, read-only tool with an output schema present, the description covers what is needed to select and invoke it. The only real gap is disambiguation from system_status_tool, which is a selection concern rather than a completeness one.

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 tool takes no parameters, which is the baseline-4 case; nothing needs explaining. The description correctly signals that the call is argument-free by listing only outputs.

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 ('Get host identity info') plus the concrete fields returned (hostname, kernel, OS), so an agent knows exactly what it yields. It does not differentiate itself from the closest sibling, system_status_tool, which an agent might reasonably consider an alternative.

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?

Usage is only implied by the resource name; there is no statement of when to prefer this over system_status_tool or session_list_tool, and no prerequisites or exclusions. Adequate for a zero-argument read, but inference is required.

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