get_top_network_info

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

With no annotations, the description carries the full disclosure burden and provides almost nothing: it does not state that this is a non-mutating read (only implied by "Get"), what the overview contains, or whether it fails on an invalid node_path. For a zero-annotation tool this is a substantive gap.

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?

One short, front-loaded sentence with no filler, so it is structurally clean. The brevity reflects under-specification rather than disciplined economy, since nothing about scope, inputs, or returns is covered.

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 tool is simple (one required param, read-only by implication), but with no annotations, no output schema, and 0% schema coverage, the definition leaves both the input meaning and the returned content undefined. A single vague sentence is not enough for an agent to invoke this confidently.

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 single required parameter node_path has 0% schema description coverage, and the description never mentions it — it does not say whether the path points to a TOP network, a TOP node, or a filesystem-style subnetwork path. The parameter name alone is the only clue the agent gets.

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 supplies a verb ("Get") and a resource ("overview of a TOP network"), so the general intent is legible. But "overview" never says what is included, and it does not distinguish this from the sibling get_network_overview or from get_top_scheduler_info, both of which read like adjacent ways to inspect a network.

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 when-to-use guidance at all: no prerequisite (e.g., a loaded/current network), no statement of when to prefer this over get_network_overview or get_top_scheduler_info, and no exclusions. The agent must guess from the name alone.

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