net.health

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

No annotations exist, so the description carries the full disclosure burden, yet it says nothing about whether this is a local read-only probe, whether it requires credentials or elevated privileges, or whether "config caps" exposes sensitive configuration. For a zero-parameter introspection call the risk is low, but the behavioral surface is essentially undocumented.

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?

Eight words, front-loaded, with no filler or repetition. The terseness borders on under-specification, but nothing in it is wasted.

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 and no annotations, the description is the only source of return-value information, and it names output categories vaguely ("capability matrix", "config caps") without saying what those contain or in what shape. It is minimally adequate for a no-parameter probe but leaves the agent guessing about what it will actually receive.

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 has zero parameters, so there is nothing for the description to clarify and the baseline of 4 applies. It gains no extra credit since it adds no meaning beyond the empty schema.

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 is a bare noun list of returned data ("Server version, platform, capability matrix, config caps") rather than a verb+resource statement, so an agent must infer that this tool reports the health/capability profile of the local server or agent host. It conveys the topic but does not distinguish it from the sibling wifi.health, which likely has an overlapping remit.

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?

There is no statement of when to call this versus alternatives, no prerequisites, and no indication of cost. With 32 sibling tools including wifi.health, sec.exposure and net.publicip, the agent is given no basis for choosing this one.

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